Lack of documentation on handling Merge proposals for Git

Bug #2024464 reported by Sameer Sharma
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

As suggested in the answer section, i am opening this bug report to highlight the lack of a proper documentation in launchpad on handling git merges and resolving git merge related conflicts.
This lack/deficiency may lead to a harsh and confusing situations for newcomers to launchpad and as such it will be grateful if we could have proper documentation on this topic.
There exists one for Bazaar/Breezy but not for git.
Thanks.

Jürgen Gmach (jugmac00)
Changed in launchpad:
status: New → Triaged
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.