When `next` branch falls behind `main` branch it should be automatically updated to `main` #41

New issue

Closed

opened 2024-04-13 14:41:08 +01:00 by kemitix · 0 comments

kemitix commented

2024-04-13 14:41:08 +01:00

Owner

This can happen when a PR is is merged, or some other commit lands on the main branch outside of git-next's control.

Issue the equivalent of:

git push origin origin/main:next

This can happen when a PR is is merged, or some other commit lands on the `main` branch outside of `git-next`'s control. Issue the equivalent of: ```shell git push origin origin/main:next ```

kemitix added the

labels 2024-04-13 14:41:08 +01:00

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

kemitix referenced this issue from a commit

2024-04-13 15:44:04 +01:00

feat(repo/branch): update next branch when not based on main

kemitix closed this issue

2024-04-13 15:49:05 +01:00

kemitix self-assigned this 2024-04-13 20:16:35 +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#41

No description provided.

When next branch falls behind main branch it should be automatically updated to main #41

When `next` branch falls behind `main` branch it should be automatically updated to `main` #41