-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update contributing guide to add additional instructions #206
Conversation
Signed-off-by: Kim Tsao <[email protected]>
CONTRIBUTING.md
Outdated
|
||
### Contributing | ||
1. Open an issue in the [devfile/api](https://github.com/devfile/api) repo to track adding a new stack or sample | ||
2. Avoid using container images (check for references in the Devfile and Dockerfile) from registries (like DockerHub) that impose rate limiting. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we provide more guidance, e.g. using a mirror on quay.io, to work around the problem
Signed-off-by: Kim Tsao <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: elsony, kim-tsao, maysunfaisal The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What does this PR do?:
Summarize the changes. Are any stacks or samples added or updated?
This is part of the proposed Devfile Lifecycle doc. Addressing review comments for stack providers in doc https://docs.google.com/document/d/1Syr8SZyLoVGwvZTyjHnEFm9CQ3xpQ3zBgw-PLldxsNY/edit:
Which issue(s) this PR fixes:
Link to github issue(s)
devfile/api#1066
PR acceptance criteria:
Have you read the devfile registry contributing guide and followed its instructions?
Does this repository's tests pass with your changes?
Does any documentation need to be updated with your changes?
Have you tested the changes with existing tools, i.e. Odo, Che, Console? (See devfile registry contributing guide on how to test changes)
How to test changes / Special notes to the reviewer: