KEMBAR78
Disable lint suggestions on my PRs by ezyang · Pull Request #138054 · pytorch/pytorch · GitHub
Skip to content

Conversation

@ezyang
Copy link
Contributor

@ezyang ezyang commented Oct 16, 2024

Stack from ghstack (oldest at bottom):

The suggestions unusably clog up early draft PRs that are not necessarily lint clean yet. Making matters worse, even if I fix them I have to manually click through hundreds of comments to "Resolve" them even though I've fixed it. Disabling it on ghstack helps, but I occasionally do standard PRs via fbcode export mechanism. Opt me out.

Signed-off-by: Edward Z. Yang ezyang@meta.com

[ghstack-poisoned]
@ezyang ezyang requested a review from a team as a code owner October 16, 2024 03:39
@pytorch-bot
Copy link

pytorch-bot bot commented Oct 16, 2024

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/138054

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 4ec0b8e with merge base fe43f72 (image):
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@pytorch-bot pytorch-bot bot added the topic: not user facing topic category label Oct 16, 2024
ezyang added a commit that referenced this pull request Oct 16, 2024
Signed-off-by: Edward Z. Yang <ezyang@meta.com>

ghstack-source-id: 79f8848
Pull Request resolved: #138054
@ezyang ezyang requested review from PaliC, kit1980 and malfet October 16, 2024 03:39
Copy link
Contributor

@huydhn huydhn left a comment

Choose a reason for hiding this comment

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

Just FYI, there is an issue to improve the UX here pytorch/test-infra#5760. But, till it's done, opt-out it is then.

Copy link
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.

image

pull-requests: write
runs-on: lf.linux.2xlarge
if: ${{ github.repository_owner == 'pytorch' }}
if: ${{ github.repository_owner == 'pytorch' && github.event.pull_request.user.login != 'ezyang' }}
Copy link
Contributor

Choose a reason for hiding this comment

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

Please...

Suggested change
if: ${{ github.repository_owner == 'pytorch' && github.event.pull_request.user.login != 'ezyang' }}
if: ${{ github.repository_owner == 'pytorch' && github.event.pull_request.user.login != 'ezyang' && github.event.pull_request.user.login != 'malfet' }}

Copy link
Collaborator

Choose a reason for hiding this comment

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

Can we just not run them on draft PRs?

Copy link
Contributor

Choose a reason for hiding this comment

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

May be the right solution is just to disable the workflow or make it an opt-in. Or perhaps run it only if your workflows needs approval...

Copy link
Contributor Author

Choose a reason for hiding this comment

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

sure

Copy link
Contributor Author

Choose a reason for hiding this comment

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

a sensible opt-in strategy is have the lint error ci message say "to suggest these as changes on your PR, comment BLAH" and then the flow triggers on that

@albanD albanD removed their request for review October 16, 2024 13:58
[ghstack-poisoned]
ezyang added a commit that referenced this pull request Oct 17, 2024
Signed-off-by: Edward Z. Yang <ezyang@meta.com>

ghstack-source-id: d6f7431
Pull Request resolved: #138054
@ezyang
Copy link
Contributor Author

ezyang commented Oct 17, 2024

@pytorchbot merge

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Oct 17, 2024
@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

@pytorchmergebot
Copy link
Collaborator

This PR (#138054) was merged in 38d9924 but it is still open, likely due to a Github bug, so mergebot is closing it manually. If you think this is a mistake, please feel free to reopen and contact Dev Infra.

YUNQIUGUO pushed a commit to YUNQIUGUO/pytorch that referenced this pull request Oct 17, 2024
The suggestions unusably clog up early draft PRs that are not necessarily lint clean yet. Making matters worse, even if I fix them I have to manually click through hundreds of comments to "Resolve" them even though I've fixed it. Disabling it on ghstack helps, but I occasionally do standard PRs via fbcode export mechanism. Opt me out.

Signed-off-by: Edward Z. Yang <ezyang@meta.com>
Pull Request resolved: pytorch#138054
Approved by: https://github.com/huydhn, https://github.com/malfet, https://github.com/PaliC
@github-actions github-actions bot deleted the gh/ezyang/2969/head branch November 17, 2024 02:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/trunk Trigger trunk jobs on your pull request Merged topic: not user facing topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants