mirror of https://github.com/k3s-io/k3s
make godep happy
Daniel Smith
parent
52a96d95c0
commit
3bb1059179
File diff suppressed because it is too large
Load Diff
|
|
@ -1,10 +0,0 @@
|
|||
{
|
||||
"Rules": [
|
||||
{
|
||||
"SelectorRegexp": "k8s[.]io",
|
||||
"AllowedPrefixes": [
|
||||
"k8s.io/gengo"
|
||||
]
|
||||
}
|
||||
]
|
||||
}
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
language: go
|
||||
go:
|
||||
- 1.6
|
||||
- 1.7
|
||||
- tip
|
||||
|
||||
go_import_path: k8s.io/gengo
|
||||
|
||||
script:
|
||||
- go test -v ./...
|
||||
- go run ./examples/set-gen/main.go -i k8s.io/gengo/examples/set-gen/sets/types -o ./examples/set-gen/sets --verify-only
|
||||
- go run ./examples/import-boss/main.go -i k8s.io/gengo/... --verify-only
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
assignees:
|
||||
- lavalamp
|
||||
- wojtek-t
|
||||
|
|
@ -1,50 +0,0 @@
|
|||
# gengo
|
||||
|
||||
[![Travis Widget]][Travis] [![GoDoc Widget]][GoDoc]
|
||||
|
||||
[Travis]: https://travis-ci.org/kubernetes/gengo
|
||||
[Travis Widget]: https://travis-ci.org/kubernetes/gengo.svg?branch=master
|
||||
[GoDoc]: https://godoc.org/k8s.io/gengo
|
||||
[GoDoc Widget]: https://godoc.org/k8s.io/gengo?status.svg
|
||||
|
||||
A package for generating things based on go files. This mechanism was first used
|
||||
in Kubernetes and is split out here for ease of reuse and maintainability.
|
||||
|
||||
`go get k8s.io/gengo`
|
||||
|
||||
## Examples
|
||||
|
||||
A set generator, deep-copy generator, and go-to-protobuf generator are included
|
||||
here. Also, import-boss will enforce arbitrary rules about import trees.
|
||||
|
||||
## args/
|
||||
|
||||
Package args defines common arguments for a generator binary.
|
||||
|
||||
## generator/
|
||||
|
||||
Package generator defines interfaces for code generators to implement, and
|
||||
machinery that will execute those code generators.
|
||||
|
||||
## types/
|
||||
|
||||
Package types contains the type system definition. It is modeled after Go's type
|
||||
system, but it's intended that you could produce these types by parsing
|
||||
something else, if you want to write the parser/converter.
|
||||
|
||||
We don't directly use the go types in the go typecheck library because they are
|
||||
based on implementing differing interfaces. A struct-based format is more
|
||||
convenient input for template driven output.
|
||||
|
||||
## parser/
|
||||
|
||||
Package parser parses go source files.
|
||||
|
||||
## namer/
|
||||
|
||||
Package namer defines a naming system, for:
|
||||
* helping you reference go objects in a syntactically correct way
|
||||
* keeping track of what you reference, for importing the right packages
|
||||
* and defining parallel tracks of names, for making public interfaces and
|
||||
private implementations.
|
||||
|
||||
|
|
@ -1,58 +0,0 @@
|
|||
## Kubernetes Community Code of Conduct
|
||||
|
||||
### Contributor Code of Conduct
|
||||
|
||||
As contributors and maintainers of this project, and in the interest of fostering
|
||||
an open and welcoming community, we pledge to respect all people who contribute
|
||||
through reporting issues, posting feature requests, updating documentation,
|
||||
submitting pull requests or patches, and other activities.
|
||||
|
||||
We are committed to making participation in this project a harassment-free experience for
|
||||
everyone, regardless of level of experience, gender, gender identity and expression,
|
||||
sexual orientation, disability, personal appearance, body size, race, ethnicity, age,
|
||||
religion, or nationality.
|
||||
|
||||
Examples of unacceptable behavior by participants include:
|
||||
|
||||
* The use of sexualized language or imagery
|
||||
* Personal attacks
|
||||
* Trolling or insulting/derogatory comments
|
||||
* Public or private harassment
|
||||
* Publishing other's private information, such as physical or electronic addresses,
|
||||
without explicit permission
|
||||
* Other unethical or unprofessional conduct.
|
||||
|
||||
Project maintainers have the right and responsibility to remove, edit, or reject
|
||||
comments, commits, code, wiki edits, issues, and other contributions that are not
|
||||
aligned to this Code of Conduct. By adopting this Code of Conduct, project maintainers
|
||||
commit themselves to fairly and consistently applying these principles to every aspect
|
||||
of managing this project. Project maintainers who do not follow or enforce the Code of
|
||||
Conduct may be permanently removed from the project team.
|
||||
|
||||
This code of conduct applies both within project spaces and in public spaces
|
||||
when an individual is representing the project or its community.
|
||||
|
||||
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting a Kubernetes maintainer, Sarah Novotny <sarahnovotny@google.com>, and/or Dan Kohn <dan@linuxfoundation.org>.
|
||||
|
||||
This Code of Conduct is adapted from the Contributor Covenant
|
||||
(http://contributor-covenant.org), version 1.2.0, available at
|
||||
http://contributor-covenant.org/version/1/2/0/
|
||||
|
||||
### Kubernetes Events Code of Conduct
|
||||
|
||||
Kubernetes events are working conferences intended for professional networking and collaboration in the
|
||||
Kubernetes community. Attendees are expected to behave according to professional standards and in accordance
|
||||
with their employer's policies on appropriate workplace behavior.
|
||||
|
||||
While at Kubernetes events or related social networking opportunities, attendees should not engage in
|
||||
discriminatory or offensive speech or actions regarding gender, sexuality, race, or religion. Speakers should
|
||||
be especially aware of these concerns.
|
||||
|
||||
The Kubernetes team does not condone any statements by speakers contrary to these standards. The Kubernetes
|
||||
team reserves the right to deny entrance and/or eject from an event (without refund) any individual found to
|
||||
be engaging in discriminatory or offensive speech or actions.
|
||||
|
||||
Please bring any concerns to to the immediate attention of Kubernetes event staff
|
||||
|
||||
|
||||
[]()
|
||||
Loading…
Reference in New Issue