How can i mark all gitlab alters as Resolved for my project?
There's no button to select and mark all alerts in monitor -> alerts
Related
It seems like I am facing a bug within my Azure Devops repository.
Within my pull request I have merge conflicts.
Every time I solve these and resolve the matching comment, a new merge conflict appears.
Here you can see I resolved all the issues:
Next when I return to the overview page a new merge conflict is shown:
When I solve this and go back to the overview page a new merge conflict is shown.
This keeps on happening.
It is not a bug in Azure DevOps but Way of Working.
Every conflict when manually resolved from the AzureDevops Conflicts tab, will have a comment created. Before completing the PR approval, the peer reviewer needs to resolve this comment related to the conflict resolution.
I've been using Azure Pipelines for a while now and haven't changed my azure-pipelines.yml file here in 2 months. Previously, when there was a new PR, the pipeline would trigger and cause the environment to be built and the tests would be run.
Today, there was a new PR but I noticed that the pipeline was not being triggered. Then, to further test this, I forked, cloned, and branched the repository myself and created another new PR and, again, the pipeline was not triggered.
It's not clear to me where things are getting stuck and it's not clear how one would debug this. I've gone through this Azure DevOps documentation but it wasn't useful. I can manually trigger the pipeline to execute and test the master branch but I don't know how to manually trigger the same thing for a PR. Here's my Azure DevOps page for reference.
As normal, you do not need config pr in YAML script if there's no any special demand, we would do pull request trigger for all branches. But, it start broken from 03-13 21:02 (UTC), which caused by us, you do not do anything wrong.
The fix is preparing with our best.
As Alex said, this is the implicit trigger which YAML support only, if you do not configure pr in YAML explicitly.
To avoid such stuck later, except the method that Alex mentioned: add pr into YAML. You can also make use of UI configuration which performance is very stable until now.
Just go Pipeline definition page => Click on three dots of right corner => Select Trigger:
Then you will see Triggers tab which has Continues integration and Pull request validation display below. Open Pull request validation and enable Override the YAML pull request trigger from here:
Additional, Our team has noticed this broken issue, will update whether it is fixed here once we have any fixed release in progress.
Update 3/18/2020:
Fixed has released to all region. Every one can work github pr trigger as the document shows now.
I'm using GitLab web IDE, but every time I want to commit my changes the default option is: "Create a new branch", with "Start new merge request" option checked.
I want to push on develop branch, then I switch manually every time to develop... but this boring :(
But before it was automatically "Commit to develop branch".
Is there a solution to restore the previous configuration? thx
When the Web IDE tab is open then the default option for the submit is to create a new branch. But if I choose the other option, then the next commits will keep my selection as the default one.
You can simply set develop as the default branch. The default branch is the branch that changes will automatically be merged into and it's the branch that automatically opens when visiting the GitLab web interface.
These are the steps:
Choose in the leftside menue bar "Settings > Repository > Default Branch"
Determine your default branch
I have a problem with my releases in GitLab.
I created them in my project with tags. Now I want to remove them, so I deleted the associated tags but my releases are always displayed. I searched on Google and Stack Overflow but I can't find any solutions.
How can I remove these releases without their tags?
Go to Project Overview -> Releases
Click the release you want to delete
Scroll to the bottom. Find the tag icon. Click on the tag.
There is a trash can button for the tag. Deleting the tag will delete the release as well.
By now you can delete releases properly using the API:
https://docs.gitlab.com/ee/api/releases/#delete-a-release
Currently (GitLab v11.9.8) you can't. It's silly, I know, but you can't.
Ivan came up with a workaround if you have only a few releases to delete. His steps are copied below.
Ivan Kostrubin (#ovitente):
For fixing this issue you have to go through those steps
Create tag with the same name and release message that was in release, you will be able to edit this tag.
Open tag's release message for editing
Remove all text
Save it
And release has gone from the release list.
Then you can freely delete tag.
Source:
https://gitlab.com/gitlab-org/gitlab-ce/issues/58549#note_160000873
Check out these GitLab issues:
[#58549] Deleting releases with removed TAG in Release API
[#56026] Make it possible to add/edit/delete a release using the UI
Maybe I'm late but I've created a chrome extension that allows you to do just that, hope it helps :)
https://github.com/tuanddd/grru
Go to Repository -> Tags on the left side Collapse sidebar. Then click on the delete icon on the right of the tag name.
Example:
GitLab 15.3 (August 2022) should improve release management:
Releases usability improvements
In 15.3, we made several improvements that made GitLab Releases easier to use.
Users can now:
delete a release directly in the UI,
set the release date in the UI,
edit the release_at date in the UI, and
easily identify a historical release.
See Documentation, Issue, Issue, Issue and Issue.
For instance: Delete a release, starting with GitLab 15.2:
When you delete a release, its assets are also deleted. However, the associated Git tag is not deleted.
Prerequisites:
You must have at least the Developer role. Read more about Release permissions.
To delete a release in the UI:
On the top bar, select Menu > Projects and find your project.
On the left sidebar, select Deployments > Releases.
In the top-right corner of the release you want to delete, select Edit this release ().
On the Edit Release page, select Delete.
Select Delete release
gitlab-scripts repo
I created a bash script that will remove all releases given a repo name,
purge/releases.sh
There are similarly named purge/tags.sh and purge/packages.sh in the repo. You can call any of them like this,
GITLAB_TOKEN="mytoken" ./reset-repo.sh <repo>
Use the gitlab gem.
gem install gitlab
gitlab delete_project_release 1234 'v1.2.3'
I've just started using GitLab, and have created a set of issues, in order to keep an overview of what needs to be done for my application. I was wondering if it was possible to create a branch from these issues, such that the branch and issues are linked, similar as in jira and Stash from atlassian?
If you create a branch with the name <issue-number>-issue-description and push that branch to gitlab, it will automatically be linked to that issue. For instance, if you have an issue with id 654 and you create a branch with name 654-some-feature and push it to gitlab, it will be linked to issue 654.
Gitlab will even ask you if you want to create a merge request and will automatically add Closes #654 to the merge request description which will close issue 654 when the merge request is accepted.
Also if you go to a given issue page on gitlab, you should see a New Branch button which will automatically create a branch with a name of the form <issue-number>-issue-description.
On the Issue screen, you see a green button labeled "Create merge request", with a down-arrow to its right.
That's not a button, that's a drop down list of buttons.
Click on the down arrow
Choose "Create branch"
Click on "Create branch"
A branch is created from the issue number, plus the title of the branch
For example, my issue #2, with title "Test repoSearch with no repos"
will have a branch called:
2-test-reposearch-with-no-repos
Notice that it changes case to all-lower-case
TLDR: do a merge request add #2 in the title and/or in the comment box and/or the commit message and it will link the issue to the branch and commit, you could just do a MR right from the start to link it.
It seems the only option for Gitlab is name your branch following this format: <issue-number-some-branch> like 2-bad-ai this will autolink the branch to the issue.
However, I organize my branches so they live nicely in the .git/ref/heads folder structure like this feature/2-<some-branch> then when you do a merge request add #2 in the title and/or in the comment box and/or the commit message and it will link the issue to the branch and commit, you could just do a MR right from the start to link it.
$ ls .git/refs/heads/; ls .git/refs/remotes/upstream/
2-bad-ai dev feature/ hotfix/ master release/
2-bad-ai dev feature/ hotfix/ master release/
I'd much rather have feature/2-bad-ai in the above output...
From what I can tell on Github you can link pull-request to feature/2-<some-branch> but doesn't have the autolinking of 2-<some-branch> like GitLab
2017:
If you create a branch with the name -issue-description and push that branch to GitLab, it will automatically be linked to that issue.
This is now customizable, with GitLab 15.6 (November 2022):
Configure default names for branches created from issues
Define a custom template for naming branches created from issues. The previous setting {issue ID}-{issue-title-hyphenated} remains the default.
To define a custom template for your project, go to Repository Settings > Branch defaults.
See Documentation and Issue.