-
Notifications
You must be signed in to change notification settings - Fork 9
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
feat: PR checks #56
feat: PR checks #56
Conversation
Signed-off-by: nadine.loepfe <[email protected]>
Signed-off-by: nadine.loepfe <[email protected]>
Signed-off-by: nadine.loepfe <[email protected]>
Signed-off-by: nadine.loepfe <[email protected]>
Signed-off-by: nadine.loepfe <[email protected]>
Signed-off-by: nadine.loepfe <[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.
a)Suggested @ Readme, from line 620:
1. Volunteer and get assigned to an open issue.
2. Fork this repository.
3. Create a new branch with your feature or fix.
4. Make your changes and follow commit naming procedures.
5. Ensure the tests pass.
6. Ensure commits are squashed and GPG-signed
7. Submit a pull request
Would also suggest some guidance on squashing, signing and naming in readme (maybe a separate contribute readme).
Can be done separately. I can raise PR if desired. Would suggest a readme users and readme for contributors.
b) is contents: write permission necessary for title checks?
hey @exploreriii ! that's on another branch, to keep things separate. |
Signed-off-by: nadine.loepfe <[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.
Approved, looking forward to working with these new checks
No description provided.