Skip to content
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

docs: Create Contribution Guidelines #49

Merged
merged 10 commits into from
Apr 26, 2021
Merged

Conversation

ScottBrenner
Copy link
Owner

@ScottBrenner ScottBrenner commented Apr 24, 2021

@ScottBrenner ScottBrenner requested a review from NickLiffen April 24, 2021 22:07
@ScottBrenner ScottBrenner added documentation Improvements or additions to documentation enhancement New feature or request labels Apr 24, 2021
@NickLiffen
Copy link
Collaborator

I think in the Issue Template we need to ask some more specific questions such as:

  1. What GitHub Actions OS is this on? (windows/mac/linux).
  2. What inputs did you pass in to the action?
  3. What version of the GitHub Action are you using?

I think they would be useful 👍

@NickLiffen
Copy link
Collaborator

@ScottBrenner thoughts on increasing the scope of this pull request to the following:

  • Moving the contributing section out to a CONTRIBUTING.md. Something like this.
  • Creating a pull request template. Even something basic like this. Some cool instructions can also be found here.
  • Creating a code of conduct. There are a few examples here.

@ScottBrenner ScottBrenner changed the title docs: Create Issue Templates docs: Create Contribution Guidelines Apr 25, 2021
@ScottBrenner
Copy link
Owner Author

Added a bunch of things from https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions, most of it's automatically generated - open to changing the wordings.

@NickLiffen
Copy link
Collaborator

@ScottBrenner Content looks really good 👍

If you have this locally, you just need to run:

npm run all

This will fix the failing tests. It is failing due to prettier errors 👍

@ScottBrenner
Copy link
Owner Author

Whoops, think a484aa6 fixed it? 😵

@ScottBrenner ScottBrenner requested a review from NickLiffen April 25, 2021 18:40
**Screenshots**
If applicable, add screenshots to help explain your problem.

**GitHub Actions Runner configuration (please complete the following information):**
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
**GitHub Actions Runner configuration (please complete the following information):**
**GitHub Actions job configuration (please complete the following information):**

Not sure what the correct terminology is here, but we want details of the environment that the Action is running in


Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported to the community leaders responsible for enforcement at
[email protected].
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A contact method was required here, when generating the file thru GitHub

@@ -0,0 +1,9 @@
## Contributing

This product welcomes contributions the any open source community. Firstly, please raise an issue on the repository, as this will be used to discuss/agree on scope and feature/bug detail. Once agreed, please follow the [Running Locally](#running-locally) steps above to get started on your machine. Branch off `main` following logically branch naming conventions `feature/***` or `bug/***`. When contributing please try and meet these development principles:
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This product welcomes contributions the any open source community. Firstly, please raise an issue on the repository, as this will be used to discuss/agree on scope and feature/bug detail. Once agreed, please follow the [Running Locally](#running-locally) steps above to get started on your machine. Branch off `main` following logically branch naming conventions `feature/***` or `bug/***`. When contributing please try and meet these development principles:
This product welcomes contributions the any open source community. Firstly, please raise an issue on the repository, as this will be used to discuss/agree on scope and feature/bug detail. Once agreed, please follow the Development section's steps in [README.md](README.md) to get started. Branch off `main` following logically branch naming conventions `feature/***` or `bug/***`. When contributing please try and meet these development principles:

NickLiffen
NickLiffen previously approved these changes Apr 26, 2021
@ScottBrenner ScottBrenner force-pushed the feat/issue-templates branch from a484aa6 to d27e5e6 Compare April 26, 2021 15:58
@ScottBrenner ScottBrenner merged commit 4fed8b1 into main Apr 26, 2021
@ScottBrenner ScottBrenner deleted the feat/issue-templates branch April 26, 2021 15:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants