kemitix/git-next
1
1
Fork 0
Code Issues 18 Pull requests 3 Projects 1 Releases 42 Packages 2 Wiki Activity Actions

Reset next to next commit towards dev when dev is not child of next #111

New issue
Closed
opened 2024-07-25 07:44:33 +01:00 by kemitix · 0 comments
kemitix commented 2024-07-25 07:44:33 +01:00
Owner
Copy link

This happens when the commit that the next branch is on is updated and the dev branch' history is rewritten.

The current implementation resets the next branch back to the main branch, then pushes it towards the dev branch. This results in CI being triggered for the commit on the tip of the main branch when it isn't needed.

Combine these two operations (reset and push) into a single update.

This happens when the commit that the `next` branch is on is updated and the `dev` branch' history is rewritten. The current implementation resets the `next` branch back to the `main` branch, then pushes it towards the `dev` branch. This results in CI being triggered for the commit on the tip of the `main` branch when it isn't needed. Combine these two operations (reset and push) into a single update.
kemitix self-assigned this 2024-07-25 07:44:33 +01:00
kemitix added this to the Road to v1 - Forgejo & Github project 2024-07-25 07:44:33 +01:00
kemitix added the
Kind/Enhancement
 label 2024-07-25 07:44:38 +01:00
kemitix added this to the NEXT-RELEASE milestone 2024-07-26 19:18:58 +01:00
kemitix modified the milestone from NEXT-RELEASE to v0.12.0 2024-07-28 20:57:05 +01:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
renovate/kxio-4.x
release-plz-2024-12-12T08-25-48Z
dev
next
renovate/docker.io-woodpeckerci-plugin-docker-buildx-5.x
v0.14.0-rc1
v0.13.11
v0.13.10
v0.13.9
v0.13.8
v0.13.7
v0.13.6
v0.13.5
v0.13.4
v0.13.3
v0.13.2
v0.13.1
v0.13.0
v0.12.1
v0.12.0
v0.11.0
v0.10.0
v0.9.4
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.1
v0.8.0
v0.7.1
v0.7.0
v0.6.2
v0.6.1
v0.6.0
v0.5.2
v0.5.1
v0.5.0
v0.4.1
v0.4.0
v0.3.3
v0.3.2
v0.3.1
v0.3.0
v0.2.0
v0.1.2
v0.1.1
v0.1.0
Labels
Clear labels   
Forge
ForgeJo
Issue relates to the ForgeJo integration

  
Forge
GitHub
Issue relates to the GitHub integration

  
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/TUI

   
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No labels
Forge
ForgeJo
Forge
GitHub
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/TUI
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No milestone
v0.12.0
Projects
Clear projects
No items
No project
Road to v1 - Forgejo & Github
Assignees
Clear assignees
No assignees
kemitix
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#111
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?