Skip to content

git, feature_branch_workflow.md: remove empty line #1908

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Mar 8, 2024
Merged

git, feature_branch_workflow.md: remove empty line #1908

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6a9a7fb
git, feature_branch_workflow.md: remove empty line
SergeCroise Mar 8, 2024
c5f10a9
git, fork_and_branch_workflow.md: remove empty line
SergeCroise Mar 8, 2024
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
3 changes: 1 addition & 2 deletions docs/gemstones/git/feature_branch_workflow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,6 @@ tags:
- git add
- git pull
- git checkout
-
---

## Feature Branch Workflow
Expand Down Expand Up @@ -83,4 +82,4 @@ The high-level steps involved are:

- Streamlines contributions for regular contributors with direct repository access.
- Ensures each feature is reviewed before being integrated into the main codebase.
- Helps maintain a clean and linear project history.
- Helps maintain a clean and linear project history.
3 changes: 1 addition & 2 deletions docs/gemstones/git/fork_and_branch_workflow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,6 @@ tags:
- git pull
- git checkout
- gh repo
-
---

## Fork and Branch Workflow
Expand Down Expand Up @@ -94,4 +93,4 @@ Benefits:

- Isolates development work to specific branches, keeping the main branch clean.
- Makes it easier to review and integrate changes.
- Reduces the risk of conflicts with the main project’s evolving codebase.
- Reduces the risk of conflicts with the main project’s evolving codebase.