Overview of the Suggestion
https://github.com/wei/pull
Every time I make a Pull Request to develop, I noticed that its a pain to keep in sync with the branch because of how quickly pushes are made to it because of the sheer scale of this project. The last time I opened a PR, within 5 minutes 200 commits were made, and my branch was already out of sync and all the tests broke. Every single time I had to rebase and force-push which I felt was tedious manual work. So I looked up some ways on how other repositories deal with this. Turns out, there are multiple apps and GitHub actions designed exactly for this issue. They automatically sync every fork with the upstream branch. I noticed that other contributors are also chasing ghost issues where tests fail, but suddenly pass when their feature branch is rebased. This could make life easier for everyone opening PRs into the develop branch. Does IQSS think this is a good idea? Just a suggestion that I think could help developer experience.
What kind of user is the suggestion intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Dataverse Developers
What inspired this idea?
Pain
What existing behavior do you want changed?
Pull Request Behavior
Any brand new behavior do you want to add to Dataverse?
N/A
Any open or closed issues related to this suggestion?
N/A
Are you thinking about creating a pull request for this issue?
Help is always welcome, is this idea something you or your organization plan to implement?
N/A
Overview of the Suggestion
https://github.com/wei/pull
Every time I make a Pull Request to develop, I noticed that its a pain to keep in sync with the branch because of how quickly pushes are made to it because of the sheer scale of this project. The last time I opened a PR, within 5 minutes 200 commits were made, and my branch was already out of sync and all the tests broke. Every single time I had to rebase and force-push which I felt was tedious manual work. So I looked up some ways on how other repositories deal with this. Turns out, there are multiple apps and GitHub actions designed exactly for this issue. They automatically sync every fork with the upstream branch. I noticed that other contributors are also chasing ghost issues where tests fail, but suddenly pass when their feature branch is rebased. This could make life easier for everyone opening PRs into the develop branch. Does IQSS think this is a good idea? Just a suggestion that I think could help developer experience.
What kind of user is the suggestion intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Dataverse Developers
What inspired this idea?
Pain
What existing behavior do you want changed?
Pull Request Behavior
Any brand new behavior do you want to add to Dataverse?
N/A
Any open or closed issues related to this suggestion?
N/A
Are you thinking about creating a pull request for this issue?
Help is always welcome, is this idea something you or your organization plan to implement?
N/A