When `next` branch is not an ancestor of `dev` it should be force updated back to `main` #21

New issue

Closed

opened 2024-04-10 09:11:38 +01:00 by kemitix · 0 comments

kemitix commented

2024-04-10 09:11:38 +01:00

Owner

No description provided.

kemitix added the

Kind/Feature

label 2024-04-10 09:11:38 +01:00

kemitix changed title from ~~When `next` status checks fail, reset to `main` and wait for `dev` to be updated~~ to When `next` branch is not an ancestor of `dev` it should be force updated back to `main`

2024-04-11 14:17:45 +01:00

kemitix referenced this issue from a commit

2024-04-11 15:46:13 +01:00

feat: Force push next branch to main when it isn't a dev ancestor

kemitix referenced this issue from a commit

2024-04-11 15:48:32 +01:00

feat: Force push next branch to main when it isn't a dev ancestor

kemitix closed this issue

2024-04-11 15:53:08 +01:00

kemitix self-assigned this 2024-04-11 18:24:12 +01:00

kemitix added this to the v0.1.0 - Dog Food milestone 2024-04-11 18:35:22 +01:00

kemitix added this to the Road to v1 - Forgejo & Github project 2024-04-13 14:42:04 +01:00

No milestone

No project

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: kemitix/git-next#21

No description provided.

When next branch is not an ancestor of dev it should be force updated back to main #21

When `next` branch is not an ancestor of `dev` it should be force updated back to `main` #21