How ambujmishra1997/devops-git-workflow works
This repository demonstrates a Git/GitHub workflow, with a small Bash system-information script as its practical feature. The primary documented path is feature work submitted by pull request to dev, then promoted by pull request to main and tagged as a release. Separate branches cover issue tracking, documentation, ignore rules, and release-history records. The README documents these relationships and shows the script’s commands; no source excerpts were provided, so implementation details beyond that are not inferred.
Main entry points: system-info.sh System info script · branching-strategy.md Branching guide · git-commands.md Git command guide · CHANGELOG.md Release history
Components 14
Git workflow
- Feature branches
- dev branch
- main branch
- Pull requests
- Release tags
- Issue tracking
System information
- System info script
scripts/system-info.sh
Project documentation
- Ignore rules
.gitignore - Branching guide
docs/branching-strategy.md - Git command guide
docs/git-commands.md - Release history
CHANGELOG.md - Project overview
README.md
Other components
- Contributor
- GitHub
Connections 14
- Contributor → Feature branches: creates work
README.md - Feature branches → Pull requests: submits changes
README.md - Pull requests → GitHub: uses
README.md - Pull requests → dev branch: merges into
README.md - dev branch → Pull requests: promotes through
README.md - Pull requests → main branch: merges into
README.md - main branch → Release tags: receives tags
README.md - Contributor → Issue tracking: tracks work
README.md - Issue tracking → GitHub: uses
README.md - Feature branches → System info script: develops
README.md - Contributor → Branching guide: documents workflow
README.md - Contributor → Git command guide: documents commands
README.md - Contributor → Release history: records releases
README.md - Contributor → Project overview: documents project
README.md