External/card-drop
5
0
Fork 0
Code Issues 45 Pull requests Projects 1 Releases 28 Packages Wiki Activity Actions

AS a developer, I want there to be a hotfix CI/CD action #406

New issue
Open
opened 2024-11-17 14:16:24 +00:00 by Vylpes · 0 comments
Vylpes commented 2024-11-17 14:16:24 +00:00
Owner
Copy link

Epic:
Story Points: 2

SO THAT I can test hotfixes in the staging bot

Acceptance Criteria

GIVEN I am a developer
WHEN I push a commit to a hotfix/* branch
THEN the actions workflow will stop the existing stage bots
AND deploy the hotfix slot

Subtasks

  • Create hotfix/* CI/CD flow
  • Update develop flow to account for hotfix/*
  • Update documentation

Notes

  • Different environment, but when actioned will stop the stage bot and reuse its bot credentials
Epic: \ Story Points: 2 --- SO THAT I can test hotfixes in the staging bot ## Acceptance Criteria GIVEN I am a developer WHEN I push a commit to a `hotfix/*` branch THEN the actions workflow will stop the existing stage bots AND deploy the hotfix slot ## Subtasks - [ ] Create hotfix/* CI/CD flow - [ ] Update develop flow to account for hotfix/* - [ ] Update documentation ## Notes - Different environment, but when actioned will stop the stage bot and reuse its bot credentials
Vylpes added the
type
story
needs criteria
needs estimate
needs tests
 labels 2024-11-17 14:16:28 +00:00
Vylpes changed title from Create hotfix action pipeline to AS a developer, I want there to be a hotfix action 2024-11-24 14:31:24 +00:00
Vylpes changed title from AS a developer, I want there to be a hotfix action to AS a developer, I want there to be a hotfix CI/CD action 2024-11-24 14:31:32 +00:00
Vylpes removed the
needs criteria
 label 2024-11-24 14:33:58 +00:00
Vylpes removed the
needs estimate
needs tests
 labels 2024-12-08 16:06:35 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
feature/380-use-effect
develop
release/0.9.0
v0.8.2
v0.8.1
v0.8.0
v0.7.0
v0.6.4
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.2
v0.5.1
v0.5.0
v0.4.2
v0.4.1
v0.4.0
v0.3.1
v0.3.0
v0.2.1
v0.2.0
v0.1.8
v0.1.7
v0.1.6
v0.1.5
v0.1.4
v0.1.3
v0.1.2
v0.1.1
v0.1.0
Labels
Clear labels   
blocked

   
duplicate

   
needs criteria

   
needs estimate

   
needs tests

   
question

   
requires documentation
  
type
admin

  
type
alert

  
type
bug

  
type
change

  
type
defect

  
type
dependencies

  
type
epic

  
type
spike

  
type
story

  
type
subtask

  
won't fix
No labels
blocked
duplicate
needs criteria
needs estimate
needs tests
question
requires documentation
type
admin
type
alert
type
bug
type
change
type
defect
type
dependencies
type
epic
type
spike
type
story
type
subtask
won't fix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: External/card-drop#406
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?