Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No commit on PR merge #2

Open
aremazeilles opened this issue Feb 2, 2021 · 0 comments
Open

No commit on PR merge #2

aremazeilles opened this issue Feb 2, 2021 · 0 comments
Assignees

Comments

@aremazeilles
Copy link
Member

Ping @alfonsotecnalia

I guess I updated this fork through the Github interface, but when bringing here the latest updates from the main repo, a commit got created. I think this should be avoided as it is then difficult to make sure the two branches (base fork) are synch.

Th way I solved it in beat was to undo the last commit, and force this update the remote.
I can do it again.
But it would be good to have the procedure for doing it directly and correctly from the github interface.
There are several merging options in the github interface, we should check if one is better than the other.

@aremazeilles aremazeilles self-assigned this Feb 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant