Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@tosensei The max valid time. you can selct is however globally configured. And the default which our company uses is one year.
You are right however that pushing to protected branches is stupid. It would have been a workaround since there is no auto-backmerge feature built-in and merge requests have the aforementioned problems. I will solve it without pushing to protected branches anyway, it just annoys me that such a seemingly straightforward feature requires this amount of "effort" and complexity to implement. -
@ostream You are absolutely right about that, but since my compamy does not give me time to contribute to OSS and I am not willing tonuse my spare free time to solve my company's issues, this won't happen (at least not for that feature).
Besides isn't it the point of this page to rant (or whine) about developer issues that annoy you or make you mad? -
@Katakompe well said. This platform is made to rant, but then you got all the moralizing elitists ready to pounce on you because you’re "whining" too much.
What the hell kind of tool is Gitlab? I just want to automatically backmerge hotfixes from master to development. Even fucking Bitbucket had a checkbox to enable this. But not Gitlab, no, you better create a pipeline job in your already unreadable, overcrowded pipeline yml, but oh, the checked out repo in the pipeline is a detached head and you cant push with the user that checks out there. So what, just use a project acess token which revokes after a year breaking your task and then switch origin amd branch manually. But your token-user can't push to protected branches, so create a merge request instead, which requires approvals, making the automated step no longer automated.
But dont worry, you can just use the gitlab api to overwrite the approval rules for this MR so it requires 0 approvals. But to do so you must allow everyone to be able to overwrite approval rules therefor compromising security.
And so you made a feature that should effectively be a checkbox a 40+ line CI job which compromises your repo security.
which nuthead of an architect is responsible for the way gitlab (and its CI) is designed?
rant