Remove some patterns from PrimTorch merge rules

[nkaretnikov]

Stack from ghstack:

• -> Remove some patterns from PrimTorch merge rules #111230

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

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

✅ You can merge normally! (1 Unrelated Failure)

As of commit 8e47fc4 with merge base cf6b1cd ():

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• Lint / lintrunner / linux-job (gh)

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

[nkaretnikov]

These are too general and block people's merges, as here: #110150 (comment)

[ezyang]

@pytorchbot merge -f "ci not needed"

[pytorchmergebot]

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

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