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

Protect the main branch, require pull requests #2

Open
tompollard opened this issue Aug 23, 2023 · 0 comments
Open

Protect the main branch, require pull requests #2

tompollard opened this issue Aug 23, 2023 · 0 comments

Comments

@tompollard
Copy link

As we'll be collaborating on the repository, it will be easiest to work with pull requests to the main branch. I would suggest protecting the main branch from direct commits. You can add a rule for this at: https://github.com/fredrikWHaug/consort-diagram/settings/branches

We can talk through the process of using git for development if it is helpful. Brief outline below!

Setup

To work on a new feature, bug fix, etc:

  1. make sure your main branch is up to date: git pull
  2. check out your feature branch and switch to it: git switch -c fh/mynewfeature
  3. make your improvements.
  • keep tabs on what changes you have made with git status.
  • add the changes with: git add FILENAME.
  • commit the changes with: git commit -m "my commit message".
  • git log will show you your commit log.
  1. When the changes are ready, push them with git push (you'll receive a message saying the branch doesn't yet exist on the remote server. Just follow the instructions to create the remote branch).
  2. Go to https://github.com/fredrikWHaug/consort-diagram/pulls and open your pull request.
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

No branches or pull requests

1 participant