Skip to content

Conversation

zengk95
Copy link
Contributor

@zengk95 zengk95 commented Jul 6, 2022

Addresses #80923

The alternative to this is editing the start comment to include the land checks details, but I think it might be a bit misleading because the land check branch creation might not be there when the person first clicks on it when they get a notification. This might be a bit annoying cause then the user won't be able to look at their progress.

@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Jul 6, 2022

🔗 Helpful links

✅ No Failures (0 Pending)

As of commit 2c4084e (more details on the Dr. CI page):

Expand to see more

💚 💚 Looks good so far! There are no failures yet. 💚 💚


This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

@zengk95 zengk95 marked this pull request as ready for review July 6, 2022 16:18
@zengk95 zengk95 requested a review from a team as a code owner July 6, 2022 16:18
@zengk95 zengk95 requested a review from suo July 6, 2022 16:19
Copy link
Contributor

@janeyx99 janeyx99 left a comment

Choose a reason for hiding this comment

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

I prefer the alternative with the message being more like: "@pytorchbot successfully started a merge and is creating land time checks (which may take a minute). See merge status here and track land check progress [here]."

Reason being: if for whatever reason create_land_time_check_branch doesn't run or fails or something happens between the initial read_merge_rules to this code, the user may never get this notification (and it will be inconsistent with our other bot merge commands).

@suo
Copy link
Member

suo commented Jul 7, 2022

Reason being: if for whatever reason create_land_time_check_branch doesn't run or fails or something happens between the initial read_merge_rules to this code, the user may never get this notification (and it will be inconsistent with our other bot merge commands).

But any error would be caught by the outer exception handler and put as a comment by the bot, right?

@janeyx99
Copy link
Contributor

janeyx99 commented Jul 7, 2022

Right, though having this comment be split into two places in the code still is strange. Not a big deal either way though.

@zengk95 zengk95 force-pushed the combine-merge-comment branch from 8a428e2 to 2c4084e Compare July 13, 2022 15:44
@zengk95
Copy link
Contributor Author

zengk95 commented Jul 13, 2022

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

@pytorchbot successfully started a merge job. Check the current status here

@github-actions
Copy link
Contributor

Hey @zengk95.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

facebook-github-bot pushed a commit that referenced this pull request Jul 14, 2022
Summary:
Addresses #80923

The alternative to this is editing the start comment to include the land checks details, but I think it might be a bit misleading because the land check branch creation might not be there when the person first clicks on it when they get a notification.  This might be a bit annoying cause then the user won't be able to look at their progress.

Pull Request resolved: #80965
Approved by: https://github.com/malfet

Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/7ce92d7fac4da60bec6f0ab74eb911f2a8587210

Reviewed By: DanilBaibak

Differential Revision: D37847409

Pulled By: zengk95

fbshipit-source-id: 88f2da5904caa48fe54ed1f3097233b914f1c9ef
@github-actions github-actions bot deleted the combine-merge-comment branch February 18, 2024 01:51
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.

6 participants