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

Link to examples of high quality pull requests in the pull request template #756

Open
mfisher87 opened this issue Jul 9, 2024 · 8 comments
Labels
impact: documentation Improvements or additions to documentation

Comments

@mfisher87
Copy link
Collaborator

For example, #278 does a great job of providing a complete usage example, and our PR template can guide others to do the same!

@mfisher87 mfisher87 added the impact: documentation Improvements or additions to documentation label Jul 9, 2024
@Sherwin-14
Copy link
Contributor

@mfisher87 Hey, do you have specific opinions on how we can approach this? I Think for solving this we need to have some PR'S that follow rules form PR template and we'll then just have to link to those PR'S.

@mfisher87
Copy link
Collaborator Author

The hard part is finding those PRs :) I don't know that we'll find one "perfect PR" that ticks all the boxes easily, but maybe we can find PRs that exemplify specific things from the list? For example, we have this checklist item:

  • Populate a descriptive title. For example, instead of "Updated README.md", use a
    title such as "Add testing details to the contributor section of the README".

Instead of ... such as "Add testing details ..., we could find a PR with a clear and concise title and use that as the example, and continue to find other PRs that have stellar examples of the other qualities we're looking for. What do you think?

@Sherwin-14
Copy link
Contributor

Sherwin-14 commented Jul 11, 2024

I will try to come up with a PR that follows the rubric. I think if we are able to encompass all the rules of the rubric in one single PR that would be great. I know it's the ideal case and it may not be plausible at this point in time but I think we should try!

@mfisher87
Copy link
Collaborator Author

That sounds great! Thanks for being willing to dive deep on this! ❤️

@Sherwin-14
Copy link
Contributor

That sounds great! Thanks for being willing to dive deep on this! ❤️

@mfisher87 Can we use the PR for backwards compatibility as an Ideal PR?

@mfisher87
Copy link
Collaborator Author

I think so! Based on this comment, which of our PR checklist items do you feel that PR sets a good example for?

@Sherwin-14
Copy link
Contributor

Sherwin-14 commented Sep 18, 2024

I feel my PR has proper methodology, what I mean by that is that you will have to make changes to CHANGELOG before making a PR which I guess is something that people contributing for the first time might look over. Also I feel I could have done better with some of the titles of my commits but I think they are not too bad(they are descriptive enough). These are some of things I can remember at this point in time.

@mfisher87
Copy link
Collaborator Author

mfisher87 commented Sep 19, 2024

That sounds reasonable! Would you be willing to open a PR to modify our PR template? I'm thinking maybe we could add the example PR links as sub-bullets of the checklist items e.g.

- [ ] Update `CHANGELOG.md` with details about your change in a section titled
`## Unreleased`. If such a section does not exist, please create one. Follow
[Common Changelog](https://common-changelog.org/) for your additions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact: documentation Improvements or additions to documentation
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants