Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add "dependencies" labels to DFIU-created PRs #983

Merged
merged 1 commit into from
Jun 14, 2023

Conversation

jasonschroeder-sfdc
Copy link
Contributor

@jasonschroeder-sfdc jasonschroeder-sfdc commented Jun 13, 2023

This adds "dependencies" label to DFIU-created PRs.

@jasonschroeder-sfdc jasonschroeder-sfdc marked this pull request as ready for review June 13, 2023 20:27
@codecov
Copy link

codecov bot commented Jun 13, 2023

Codecov Report

Merging #983 (430ca32) into main (15a6327) will increase coverage by 0.01%.
The diff coverage is 100.00%.

❗ Current head 430ca32 differs from pull request most recent head f847c41. Consider uploading reports for the commit f847c41 to get more accurate results

Impacted file tree graph

@@             Coverage Diff              @@
##               main     #983      +/-   ##
============================================
+ Coverage     84.60%   84.62%   +0.01%     
  Complexity      378      378              
============================================
  Files            27       27              
  Lines          1254     1255       +1     
  Branches        166      166              
============================================
+ Hits           1061     1062       +1     
  Misses          157      157              
  Partials         36       36              
Impacted Files Coverage Δ
...sforce/dockerfileimageupdate/utils/GitHubUtil.java 73.83% <100.00%> (+0.24%) ⬆️

@@ -105,6 +105,7 @@ public int createPullReq(GHRepository origRepo, String branch,
try {
GHPullRequest pullRequest = origRepo.createPullRequest(title, forkRepo.getOwnerName() + ":" + branch,
origRepo.getDefaultBranch(), body);
pullRequest.setLabels("dependencies");
Copy link
Member

Choose a reason for hiding this comment

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

can we run it against an org/repo that doesn't have dependencies label already created? Not sure If the will auto-create a new one If it doesn't exist. In the earlier version of GHE, I believe we had to create a label explicitly first and then apply it.
LGTM otherwise

Copy link
Contributor Author

Choose a reason for hiding this comment

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

As I have seen from other tools, the label would be auto-created.
I read https://docs.github.com/en/rest/issues/labels?apiVersion=2022-11-28#about-labels and didn't see anything about the label needing to exist first.

Copy link
Member

Choose a reason for hiding this comment

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

wanted to be sure about it. vaguely remember this was needed a couple of years back.
Tested it on test-temp/test/pull/1 on soma. works fine. we should be good here

@jeetchoudhary jeetchoudhary merged commit 68e6d18 into salesforce:main Jun 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants