Open mcandre opened 5 months ago
For context, we use tags so that we can trigger workflows on commits. This is a pretty old decision and I don't think it's going to be changed anytime soon, especially since workflow dispatches still require a tag or a branch. I think the only other alternative would be to use branches but I assume there was a reason we didn't do that
I don't have any experience with Atom/RSS feeds, but afaik we have a consistent naming scheme for release tags, so if possible you can filter based on that.
cc @atalman for the mangled pypi release feed?
That's ah interesting.
GitHub Actions has fairly fine grained controls for triggering workflows on various git refs.
If more complex CI/CD logic is involved beyond what the stock system includes, perhaps a shell script could help.
Cheers, Andrew
On Tue, Apr 16, 2024 at 4:59 PM clee2000 @.***> wrote:
For context, we use tags so that we can trigger workflows on commits. This is a pretty old decision and I don't think it's going to be changed anytime soon, especially since workflow dispatches still require a tag or a branch. I think the only other alternative would be to use branches but I assume there was a reason we didn't do that
I don't have any experience with Atom/RSS feeds, but afaik we have a consistent naming scheme for release tags, so if possible you can filter based on that.
cc @atalman https://github.com/atalman for the mangled pypi release feed?
— Reply to this email directly, view it on GitHub https://github.com/pytorch/pytorch/issues/123532#issuecomment-2059986150, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAABJREI2YPNYHSORMTNCC3Y5WNLNAVCNFSM6AAAAABF3UBZMCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJZHE4DMMJVGA . You are receiving this because you authored the thread.Message ID: @.***>
🚀 The feature, motivation and pitch
I want to subscribe to PyTorch releases. However, the GitHub Atom feeds for both tags and releases have a lot of extraneous noise. It appears that PyTorch is using tags to manage non-release changes, which is generating this noise in feeds.
Alternatives
An Atom / RSS feed on the PyTorch blog, that lists only articles about new PyTorch version updates, would also suffice.
As a workaround, I am trying a third location, the PyPI release feed for the "torch" package:
https://pypi.org/rss/project/torch/releases.xml
Seems that the GitHub release feed data is corrupted somehow for this project.
Additional context
No response
cc @seemethere @malfet @pytorch/pytorch-dev-infra