Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User updates RSS feed #6938

Closed
wants to merge 9 commits into from
Closed

User updates RSS feed #6938

wants to merge 9 commits into from

Conversation

rascalking
Copy link
Contributor

This addresses issue #4603.

Copy link
Contributor

@yeraydiazdiaz yeraydiazdiaz left a comment

Choose a reason for hiding this comment

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

Thanks @rascalking! 🌟

There's a minor bug to be fixed and I left of a frontend question for other maintainers.

warehouse/templates/accounts/profile.html Show resolved Hide resolved
warehouse/templates/rss/user_updates.xml Outdated Show resolved Hide resolved
warehouse/rss/views.py Outdated Show resolved Hide resolved
latest_releases = (
request.db.query(Release)
.join(Project)
.filter(Project.users.any(username=user.username))
Copy link
Member

Choose a reason for hiding this comment

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

Note that this doesn't mean that this user has made this release, but rather that this user has some role on a project that has made a release.

In #4603 the request is for both:

(I actually want 2 feeds: one for "stuff I did directly" and one for "projects I am a maintainer on that did releases", to account for projects where the actual releases are done by a bot-user, or by a release manager.)

I think it's fine if we're only implementing half of #4603 here, but we might want to think a little more about what we're calling this feed since updates is pretty generic and we might have multiple feeds here eventually.

We also might want to make it more clear on the profile page what this feed is exactly.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hrm...maybe call them "My Releases" vs. "My Projects' Releases"?

@@ -283,6 +283,13 @@ def add_policy(name, filename):
pretend.call("ses.hook", "/_/ses-hook/", domain=warehouse),
pretend.call("rss.updates", "/rss/updates.xml", domain=warehouse),
pretend.call("rss.packages", "/rss/packages.xml", domain=warehouse),
pretend.call(
"rss.user_updates",
"/user/{username}/updates.xml",
Copy link
Member

Choose a reason for hiding this comment

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

Looking at #7013, I think this should probably be /rss/user/{username}/something.xml, where something is distinctly one of the two types of feeds discussed in #4603.

@rascalking
Copy link
Contributor Author

Okay, I implemented both feeds, named them My Releases and My Projects' Releases, and updated the urls as suggested. I think this is all set, let me know if there's anything I missed.

@di
Copy link
Member

di commented Jun 12, 2020

Hi @rascalking, can you update the merge conflicts here now that #7013 has been merged? You might also want to make some updates (docs, etc.) to align more with what was merged there.

Also, after giving it some thought I think the URLs should be:

  • Uploaded Releases: https://pypi.org/rss/user/<username>/uploaded_releases.xml
  • Maintained Releases: https://pypi.org/rss/user/<username>/maintained_releases.xml

@rascalking
Copy link
Contributor Author

Sorry, I don't think I'm going to be able to finish this.

Base automatically changed from master to main January 21, 2021 18:39
@rascalking rascalking closed this Jun 24, 2021
@asottile asottile mentioned this pull request Sep 8, 2022
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.

3 participants