Skip to content
/ AGILExGIT Public template

A GitOps/IaC workflow template to easily track and manage your Project Requirements (read: Files) long after your User Stories/Bugs (read: Issues) and Change Requests (read: Pull Requests) have been closed

Notifications You must be signed in to change notification settings

kartikg33/AGILExGIT

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

16 Commits
 
 
 
 

Repository files navigation

Example Project README

Example top-level project README to demonstrate how to use this template.

Requirements

  1. Opening a new GitHub Issue MUST automatically spawn a new issue branch and a related Pull Request
  2. Merging a Pull Request MUST close the related Issue
    1. Merge Commits MUST NOT be allowed. ONLY Squash Commits (preferably rebased before merge) MUST be allowed, in order to ensure past requirements changes can be traced back to past issues.
  3. Requirements MUST ONLY be modified on issue branches in order to link changes to the appropriate Pull Request and Issue
  4. A user MUST be able to create an Issue for a new User Story (i.e. Feature Request)
  5. A user MUST be able to create an Issue to report a Bug
  6. The following setting in your GitHub repo MUST be enabled: Settings > Actions > Allow GitHub Actions to create and approve pull requests

About

A GitOps/IaC workflow template to easily track and manage your Project Requirements (read: Files) long after your User Stories/Bugs (read: Issues) and Change Requests (read: Pull Requests) have been closed

Topics

Resources

Stars

Watchers

Forks

Sponsor this project