A user creates a new git repository (on Gitlab) and shares Mastodon project using the mastodon git collaboration tools. He invites his colleagues to the git repo. A colleague clones the repo and pushes the first commit. Currently the push operation will fail because the master branch is protected by default. However the error message that the user gets has no indication of the problem.
Solution
The git command line tool produces a useful error message that indicates the the master branch is protected. Could we have a similar error message when pushing with mastodon?
TODOs
[ ] See if jgit allows to produce an equally good error message as the git command line tool.
[ ] Implement a better error message, that helps the user to identify an fix the problem.
User story
A user creates a new git repository (on Gitlab) and shares Mastodon project using the mastodon git collaboration tools. He invites his colleagues to the git repo. A colleague clones the repo and pushes the first commit. Currently the push operation will fail because the master branch is protected by default. However the error message that the user gets has no indication of the problem.
Solution
The git command line tool produces a useful error message that indicates the the master branch is protected. Could we have a similar error message when pushing with mastodon?
TODOs