You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This action has been around for some time now and is actively used by multiple large and very active projects. It has been tested in production for long enough. It's time to remove the This project is still in an early development stage note at the top of the README and release v1 of the backport action.
What should be included in v1?
IMO, a v1 release should come with a major feature or large change to the project. The main feature of the v1 release of the backport action might as well be performance (or energy efficiency). While investigating a performance regression, we researched how to use shallow clones and fetch-depth to optimize the git clone (via actions/checkout), and the git fetches to the bare minimum. These lead to small improvements for small projects and should lead to large improvements for repositories with a long history. This performance improvement is not yet production ready, but we could easily turn it into a release candidate which we can battle-test before releasing v1.
I started this project originally together with @pihme to solve a specific problem for the Zeebe team: to automatically backport pull requests merged with octopus commits. Over time, the action has also found usages outside of Camunda. To improve the visibility, I'd like to publish the action on the GitHub Marketplace. Therefore, I will move this repo under my personal account github.com/korthout. There, I will be able to take more control over the project and work towards releasing it more often.
11092: Switch to v1-rc1 of backport-action r=korthout a=korthout
## Description
<!-- Please explain the changes you made here. -->
[This pre-release](https://github.com/zeebe-io/backport-action/releases/tag/v1-rc1) has been tested with [korthout/backport-action-test](https://github.com/korthout/backport-action-test), but I'd like to battle-test it in the Zeebe project.
It should provide a considerable performance gain when performing backports. Additionally, it allows us to remove some of the inputs because they are now all optional.
You can read more about this pre-release in:
- korthout/backport-action#289
## Related issues
<!-- Which issues are closed by this PR or are related -->
NA
Co-authored-by: Nico Korthout <[email protected]>
This action has been around for some time now and is actively used by multiple large and very active projects. It has been tested in production for long enough. It's time to remove the
This project is still in an early development stage
note at the top of the README and release v1 of the backport action.What should be included in v1?
IMO, a v1 release should come with a major feature or large change to the project. The main feature of the v1 release of the backport action might as well be performance (or energy efficiency). While investigating a performance regression, we researched how to use shallow clones and fetch-depth to optimize the git clone (via actions/checkout), and the git fetches to the bare minimum. These lead to small improvements for small projects and should lead to large improvements for repositories with a long history. This performance improvement is not yet production ready, but we could easily turn it into a release candidate which we can battle-test before releasing v1.
I started this project originally together with @pihme to solve a specific problem for the Zeebe team: to automatically backport pull requests merged with octopus commits. Over time, the action has also found usages outside of Camunda. To improve the visibility, I'd like to publish the action on the GitHub Marketplace. Therefore, I will move this repo under my personal account github.com/korthout. There, I will be able to take more control over the project and work towards releasing it more often.
Checklist
korthout-fetch-depth
Optimize git fetch-depth #296v1-rc1
v1-rc2
master
tomain
v1
,v1.0
, andv1.0.0
(switch to full semantic versioning after this)The text was updated successfully, but these errors were encountered: