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

Add new PR template for sync.yml edits #742

Merged
merged 2 commits into from
Apr 5, 2024
Merged

Add new PR template for sync.yml edits #742

merged 2 commits into from
Apr 5, 2024

Conversation

kweav
Copy link
Contributor

@kweav kweav commented Apr 5, 2024

Purpose/implementation Section

What changes are being implemented in this Pull Request and what was your approach?

The changes being implemented in this pull request are

  • Created a new subdirectory PULL_REQUEST_TEMPLATE within the .github directory (because I was following this guide from GitHub)
  • Moved the pre-existing PR template into that subdirectory (renaming the file to pull_request_template_general.md and adding a header)
  • Created a new PR template (add_to_sync_template.md) within the subdirectory with a header that automatically assigns Candace and explains that sync.yml is being edited to enroll a new repository in OTTR updates
  • Adds the new template to list of documents that get cleaned up in downstream repos within the .github/workflows/starting-course.yml file because we don't want downstream repos to create issues that assign Candace for review

What GitHub issue does your pull request address?

I think this PR addresses Issue #636. I understood the issue to mean providing a specific PR template. Perhaps it would be useful to have a commit message template, but I think that the documentation does a really good job of explaining how to write a helpful commit message and commit changes to a new branch.

Tell potential reviewers what kind of feedback you are soliciting.

Does this look like a helpful addition that won't break things? If so, I can make a similar PR template (and corresponding changes) in the OTTR_Template_Websites and OTTR_Quizzes Repos.

I was specifically interested in potentially tackling this issue while working on the OTTR Cheatsheets and realizing that using a specific PR template would be something that I could include in that.

@kweav kweav requested a review from cansavvy April 5, 2024 15:52
Copy link
Contributor

github-actions bot commented Apr 5, 2024

No broken url errors! 🎉
Comment updated at 2024-04-05-15:54:01 with changes from 68f1479

Copy link
Contributor

github-actions bot commented Apr 5, 2024

No spelling errors! 🎉
Comment updated at 2024-04-05-15:54:05 with changes from 68f1479

@kweav
Copy link
Contributor Author

kweav commented Apr 5, 2024

I'm not sure why the code of conduct commit is showing up in this list. But I also just saw in changed files that it's highlighting the code of conduct addition to the starting-course.yml file.

Copy link
Contributor

github-actions bot commented Apr 5, 2024

Re-rendered previews from the latest commit:

* note not all html features will be properly displayed in the "quick preview" but it will give you a rough idea.

Updated at 2024-04-05 with changes from the latest commit 68f1479

Copy link
Collaborator

@cansavvy cansavvy left a comment

Choose a reason for hiding this comment

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

This looks great to me! I think if you merge main into your branch the part of about the code of conduct commit should now show up in these files changed. But otherwise looks ready to merge! Thanks for doing this!

@kweav kweav merged commit 700732b into main Apr 5, 2024
9 checks passed
@kweav kweav deleted the pr_template branch April 5, 2024 18:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants