.github folder maintainance #947
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Changing bug_report from markdown to yaml Adding config.yml for new issues Adding Code of Conduct and support to the README (along with tags at the top of the readme) Adding SECURITY.md Adding CODE_OF_CONDUCT.md
rooftopcellist
approved these changes
Jun 13, 2022
|
@john-westcott-iv thank you for taking the time to improve our templates & .github configs, this looks great! |
john-westcott-iv
force-pushed
the
github_folder_maintainance
branch
from
cbb397f to
ef46d7f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changing bug_report from markdown to yaml
Adding config.yml for new issues. Clicking on New Issue now gives you a list with:
This is similar to what Ansible and now AWX repos do.
Adding Code of Conduct and support sections to the README (along with tags at the top of the readme)
For the Code of Conduct I am using the Ansible CoC just like AWX does.
For Support I am officially stating for people to use the AWX mailing list and IRC. We already see numerous operator questions in the AWX mailing list. I'd be open here if the Operator wanted to use its own mailing list/IRC channels.
Adding SECURITY.md (same as AWX, pointing users to the [email protected])
Adding .github/CODE_OF_CONDUCT.md so that it properly shows up as link in the bug report form.
These changes can be previewed at https://github.com/john-westcott-iv/awx-operator-github-test/
Feel free to submit an actual issue from the issue form. Also note, some links will be off because the links take you to the main awx-operator repo which does not (yet) have these changes. So, for example, clicking on the "For debugging help or technical support" link when opening a new issue will take you to the main awx-operator README which does not have the "Get Involved" section but you can see the URL has the #get-involved anchor added.