Here is another question - How do I fix a conflict of a PR when the master evolves in between? I should be able to continue to publish new changes in my PR but loading it may remove changes that are important and break the system. So I know that I should use "do not load the package" but having a systematic process and documented workflow would really help avoid mistakes. S
On 8 Jul 2023, at 17:03, stephane ducasse <stephane.ducasse@inria.fr> wrote:
Hi
At ESUG Guillermo and Pablo will run a special talk around git. The idea is to reply to your concrete git questions.
You can reply to this mail or keep them and we will collect them during the first days of the conference.
Here are some examples of a question.
- How can I make sure that a branch on which I’m still working will not produce noise with the new version of master that came out?
- I depend on projects that are in development but I do not want to be exposed to their bugs, how can they configure their system?
- I pushed some changes I did not want. How can I revert them and keep the others?
S _______________________________________________ Esug-list mailing list -- esug-list@lists.esug.org To unsubscribe send an email to esug-list-leave@lists.esug.org