Skip to content

Skip stale check when facebook-github-bot is merging#79572

Closed
mehtanirav wants to merge 1 commit intomasterfrom
nirav_skip_stale_check
Closed

Skip stale check when facebook-github-bot is merging#79572
mehtanirav wants to merge 1 commit intomasterfrom
nirav_skip_stale_check

Conversation

@mehtanirav
Copy link
Copy Markdown
Contributor

@mehtanirav mehtanirav commented Jun 14, 2022

Summary

ShipIt jobs triggered by co-development workflows are failing to merge PRs due to stale checks. This diff skips the stale check when merge is triggered by facebook-github-bot.

Sample merge failure: #78654 (comment)

@mehtanirav mehtanirav requested a review from a team as a code owner June 14, 2022 22:28
@facebook-github-bot
Copy link
Copy Markdown
Contributor

facebook-github-bot commented Jun 14, 2022

🔗 Helpful links

✅ No Failures (0 Pending)

As of commit e806999 (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.

Copy link
Copy Markdown
Contributor

@malfet malfet left a comment

Choose a reason for hiding this comment

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

Looks good to me

Comment thread .github/scripts/trymerge.py Outdated
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
if force:
# do not wait for any pending signals if PR is closed as part of co-development process
if force or can_skip_internal_checks(pr, comment_id):

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Would we ever run into scenario where PR has failing checks that were not covered by internal jobs?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Than it should not have been landed (i.e. person overrode those errors, which is similar to --force option)

Comment thread .github/scripts/trymerge.py Outdated
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Should it simply be moved to force step?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

force would ignore failing checks on the PR. Is that acceptable?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Yes

@mehtanirav mehtanirav force-pushed the nirav_skip_stale_check branch from 2aa51af to e806999 Compare June 15, 2022 00:24
@mehtanirav
Copy link
Copy Markdown
Contributor Author

@pytorchbot merge -g

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

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

@github-actions
Copy link
Copy Markdown
Contributor

Hey @mehtanirav.
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 Jun 20, 2022
Summary:
# Summary

ShipIt jobs triggered by co-development workflows are failing to merge PRs due to stale checks.  This diff skips the stale check when merge is triggered by `facebook-github-bot`.

Sample merge failure: #78654 (comment)

Pull Request resolved: #79572
Approved by: https://github.com/bigfootjon, https://github.com/seemethere, https://github.com/malfet

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

Reviewed By: malfet

Differential Revision: D37208286

Pulled By: mehtanirav

fbshipit-source-id: a3fa3c954933c140f51c08088abcb094cde01ad0
@github-actions github-actions Bot deleted the nirav_skip_stale_check branch February 17, 2024 01:51
laurentdupin pushed a commit to laurentdupin/pytorch that referenced this pull request Apr 25, 2026
# Summary

ShipIt jobs triggered by co-development workflows are failing to merge PRs due to stale checks.  This diff skips the stale check when merge is triggered by `facebook-github-bot`.

Sample merge failure: pytorch#78654 (comment)
Pull Request resolved: pytorch#79572
Approved by: https://github.com/bigfootjon, https://github.com/seemethere, https://github.com/malfet
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