closed
merge request
!3
"Adding a failing test on a separate branch to show how pytest error messages..."
at
gitlabci_gallery / testing / pytest-gitlab-reports
commented on
merge request !3
"Adding a failing test on a separate branch to show how pytest error messages..."
at
gitlabci_gallery / testing / pytest-gitlab-reports
Indeed, it is the very same idea. I did not check in MR and it is actually a better idea to keep them in Draft MR rather than in the main branch. A...
commented on
merge request !3
"Adding a failing test on a separate branch to show how pytest error messages..."
at
gitlabci_gallery / testing / pytest-gitlab-reports
@mhaefele : is it different from the purpose of MR !1 ?
opened
merge request
!3
"Adding a failing test on a separate branch to show how pytest error messages..."
at
gitlabci_gallery / testing / pytest-gitlab-reports
opened
merge request
!2
"Draft: Create MR to view coverage on diff"
at
gitlabci_gallery / testing / pytest-gitlab-reports
opened
merge request
!1
"Draft: MR for testing failure view"
at
gitlabci_gallery / testing / pytest-gitlab-reports
created project
gitlabci_gallery / testing / pytest-gitlab-reports