Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
pull tester
  • Loading branch information
RyanTaylor37 committed Jun 2, 2023
commit 182028d4fb2fe702d279f97ef6479473951e7b48
4 changes: 2 additions & 2 deletions getting_started/git.rst
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ Each GitHub project can be considered an overarching area of focus. We have an a
Our main board for misceallaneous work items that need to get done is General. Using projects gives us a good view of what is being worked on by who and what needs to be done in the future while requiring little
maintenence on our part due to the nice automation features and ability to link pull requests to issues.

If you ever need something to work on, take a look at the projects and feel free to assign yourself to a work item or better yet, add a completely new work item!
If you ever need something to work on, take a look at the projects and feel free to assign yourself to a work item or better yet, add a completely new work item!

Branching Strategy
==================
Expand All @@ -47,4 +47,4 @@ Merging Strategy
- Try to avoid creating a merge commits when completing PRs

.. note::
After completing a PR, the branch should be deleted if it will not be used for future development. It can always be restored at a later point if needed.
After completing a PR, the branch should be deleted if it will not be used for future development. It can always be restored at a later point if needed. (Git)