Feature Overview

The Image Updater is able to persist changes in Git. However, it does so by directly pushing a commit into Git.

Many people will have branch protections in place that forbid direct pushes to their branches, and would prefer the Image Updater to create a Pull Request instead. This would enable CI checks, manual approvals and more to have an image being updated in the Application.

Goals

• Support Pull (Merge-) Request creation and tracking for GitHub and GitLab

Requirements

Use Cases

• As a user of Image Updater, I would like my updates to be submitted via PR/MR so that I can run CI checks before the change is merged into Git

Out of scope

<Defines what is not included in this story>

Dependencies

<Link or at least explain any known dependencies.>

Background, and strategic fit

<What does the person writing code, testing, documenting need to know?>

Assumptions

<Are there assumptions being made regarding prerequisites and dependencies?>

<Are there assumptions about hardware, software or people resources?>

Customer Considerations

<Are there specific customer environments that need to be considered (such as working with existing h/w and software)?>

Documentation/QE Considerations

<What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)?>

<Does this feature have a doc impact? Possible values are: New Content, Updates to existing content,  Release Note, or No Doc Impact?>

<Are there assumptions being made regarding prerequisites and dependencies?>

<Are there assumptions about hardware, software or people resources?>

Impact

<If the feature is ordered with other work, state the impact of this feature on the other work>

Related Architecture/Technical Documents

<links>

Definition of Ready

• The objectives of the feature are clearly defined and aligned with the business strategy.
• All feature requirements have been clearly defined by Product Owners.
• The feature has been broken down into epics.
• The feature has been stack ranked.
• Definition of the business outcome is in the Outcome Jira (which must have a parent Jira).

• …