this post was submitted on 06 Oct 2023
13 points (93.3% liked)

KDE

5338 readers
50 users here now

KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.

Plasma 6 Bugs

If you encounter a bug, proceed to https://bugs.kde.org/, check whether it has been reported.

If it hasn't, report it yourself.

PLEASE THINK CAREFULLY BEFORE POSTING HERE.

Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.

founded 1 year ago
MODERATORS
carlschwan@lemmy.kde.social
Bro666@lemmy.kde.social
herzenschein@pawb.social
Aniqakhokhar@lemmy.kde.social
13
question about gitlab merge request (invent.kde.org) (lemmy.kde.social)
submitted 1 year ago by tubbadu@lemmy.kde.social to c/kde@lemmy.kde.social
12 comments fedilink hide all child comments
 

Hello! Yesterday I submitted my first merge request to a KDE software! I forked the repo, applied the edits, committed them and pushed to my fork, and then from gitlab created a merge request. after a few hours, the author pushed something into the master, making my merge request 1 commit behind the master. On the merge request details page, I now get this error:

Merge blocked: the source branch must be rebased onto the target branch.  [rebase without pipeline]  [rebase]

If I try to click on [rebase], I get this red error:

Source branch is protected from force push

what should I do to make my merge request "mergeable" again?

you are viewing a single comment's thread
view the rest of the comments
[–] Zamundaaa@discuss.tchncs.de 3 points 1 year ago

Presumably, your merge request is about merging your fork master branch into the upstream master branch, right?

In that case, you have two options:

  1. Go into the Gitlab settings of your fork, find the setting where branches are protected and disable the protection for your master branch
  2. (the recommended way, at least for future merge requests) always create a feature branch, never work on master in the first place. You can create a branch from what you have right now on the command line with git checkout -b featurename. Then push that branch and create a new merge request for it