Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Conversation

@p-varma
Copy link

@p-varma p-varma commented Apr 20, 2023

MR is in Draft state
Yet to write the testcases.

Changes

Documentation and testing

Please consider whether this PR needs documentation and tests. This is not required, but highly appreciated:

@codecov
Copy link

codecov bot commented Apr 20, 2023

Codecov Report

Attention: 9 lines in your changes are missing coverage. Please review.

Comparison is base (f310764) 96.21% compared to head (ecaa566) 96.07%.
Report is 149 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2552      +/-   ##
==========================================
- Coverage   96.21%   96.07%   -0.14%     
==========================================
  Files          87       87              
  Lines        5700     5726      +26     
==========================================
+ Hits         5484     5501      +17     
- Misses        216      225       +9     
Flag Coverage Δ
api_func_v4 82.37% <66.66%> (-0.08%) ⬇️
cli_func_v4 83.02% <66.66%> (-0.09%) ⬇️
unit 87.77% <66.66%> (-0.11%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
gitlab/v4/objects/projects.py 98.86% <100.00%> (+<0.01%) ⬆️
gitlab/v4/objects/merge_trains.py 74.28% <64.00%> (-25.72%) ⬇️

Copy link
Contributor

@robinson96 robinson96 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My team is already using this branch for our workflow, so excited to have this piece of the puzzle.

FWIW - at least in current versions of Gitlab, we are seeing issues with the merge train actually being merged in if the SHA is not specified as part of the request. May consider having the SHA be required at this layer so others are able to dodge the pain.

@github-actions
Copy link

This PR was closed because it has been marked stale for 15 days with no activity. If this PR is still valid, please re-open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.