Skip to content

Conversation

@thomaskileyukaea
Copy link
Contributor

This builds on #213, but moves the detailed info about how to protect branches into an extras page.

The motivation for having this as an extra, rather than inline:

  • Too long to go in a callout, but the section was supposed to be a short primer on different repo models
  • Distracts from the goal of the episode - it is about code reviews not how to configure a GH repo.

thomaskileyukaea and others added 11 commits July 26, 2023 13:52
Since there is quite a lot of text, put under actual headings rather
than as part of the bullet point list
These instructions mean that on a shared repository the pull request
system must be used. This prevents accidentally pushing to the main
branch, as well as ensuring people get into the habbit of raising pull
requests for their changes.
… a list

Co-authored-by: Aleksandra Nenadic <a.nenadic@manchester.ac.uk>
This is quite detailed and isn't directly connected to the topic of code
review. Further, it is GitHub specific and someones repository might
already be setup correctly.
Since this text is a callout box, having full size headers feels wrong.
It is only about protecting branches, so remove padding to indicate it
might be about other GitHub settings - can be changed to that in the
future if required
This extra now only covers protecting the main branch
@anenadic
Copy link
Collaborator

Thank you @thomaskileyukaea 👍

@anenadic anenadic closed this Aug 10, 2023
@anenadic anenadic reopened this Aug 10, 2023
@anenadic anenadic merged commit 743ea89 into carpentries-incubator:gh-pages Aug 10, 2023
@thomaskileyukaea thomaskileyukaea deleted the move-branch-protection-to-extras branch August 14, 2023 10:05
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