0

Is there a way to push via Magit, so that the push will automatically produce a release in GitLab?

For example: I prepare my files, open the Magit status buffer, stage the file via s, commit the file via cc, enter my commit message and press C-cC-c.

Next I define a new, annotated and signed tag via t-a-s enter the version numberRET enter the version messageRET.

Now I can start to push everything to the remote Gitlab PT enter the previous defined version numberRET and Pp.

After having typed so, the Magit status buffer shows me, that it had pushed the new commit with the new tag. Gitlab also has the new tag with the version number and its version message. But it has not created a release of this commit/push.

To build the release, I have to go to the tags page of my Gitlab project and edit the tag in question. After having added and stored a release note, the release is finally build by Gitlab.

Is there a way, to enter the release note while definig the new tag or pushing from Magit?

6
  • 1
    What is a "release" from a Git-only perspective? If the answer is "nothing; this is a Gitlab-specific concept" then Magit possibly can't do this (but Forge might be able to).
    – phils
    Jan 25 at 3:05
  • 1
    docs.gitlab.com/ee/user/project/releases seems relevant if you need to raise a feature request.
    – phils
    Jan 25 at 3:10
  • Thank you @phils It seems to be a Gitlab specific thing to be. I will have a look at the Forge documents.
    – Jan
    Jan 25 at 10:23
  • I tried to implement Magit-Forge for Gitlab but got stuck in contacting the server, see my new question, but reading from the Manual, this will be the solution to my question
    – Jan
    Jan 25 at 15:52
  • Hopefully you will be able to post an answer to your own question here, after the new problem is resolved.
    – phils
    Jan 25 at 20:08

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.