Skip to content

Project integrations #3

Closed
Closed

Description

@hugovk

Things to do for the new repo

Activity

  1. self-assigned this
    on Apr 14, 2022
  2. changed the title [-]Integrations[/-] [+]Project integrations[/+] on Apr 14, 2022
  3. carterbox commented on May 3, 2022

    @carterbox
    Contributor

    Maybe it's too late or you already knew, but you can transfer issue from repo to repo if you have sufficient permission instead of closing and recreating them.

    https://github.com/proxy/docs.github.com/en/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository

  4. hugovk commented on May 3, 2022

    @hugovk
    MemberAuthor

    Thanks, but unfortunately issue transfer only works within the same user/org account:

    Note: You can only transfer issues between repositories owned by the same user or organization account. A private repository issue cannot be transferred to a public repository.

    Here's what I see when trying to transfer from the old repo:

    image

    image

    Both orgs contain a single repo and the dropdown was empty.

    When I check an issue in my user account, there's plenty of repos in the dropdown from my account, but I can't see either of these orgs:

    image

  5. carterbox commented on May 3, 2022

    @carterbox
    Contributor

    Oye! That's annoying! 🤦🏼

  6. hugovk commented on Jun 11, 2023

    @hugovk
    MemberAuthor

    I've opened a PEP 541 request to ask for admin access on PyPI to set up uploading via trusted publisher:

  7. hugovk commented on Jul 5, 2023

    @hugovk
    MemberAuthor

    We now have https://humanize.readthedocs.io, I've updated the RTD project to build from this repo, and updated the links: #128 🎉

    TODO as followup:

    • remove old RTD project's PR preview integration
    • redirect old RTD page to new one
  8. hugovk commented on Oct 21, 2024

    @hugovk
    MemberAuthor

    [x] PyPI and TestPyPI API tokens or trusted publisher for automated deploys: BLOCKED, need admin access to the project on PyPI: PEP 541 Request: humanize pypi/support#2916

    This is now done and I've set up Trusted Publishing: #213

  9. hugovk commented on Feb 13, 2025

    @hugovk
    MemberAuthor
    • Redirect old ReadTheDocs to new

    Final task:

    We have the docs building at both https://python-humanize.readthedocs.io/ and https://humanize.readthedocs.io/ but we only need the second one.

    I've deleted the GitHub integration at https://app.readthedocs.org/dashboard/python-humanize/integrations/ and we already have this redirect at https://app.readthedocs.org/dashboard/python-humanize/redirects/

    Image

    But it wasn't redirecting. Ah, but "Force redirect, even if a page exists" was not checked, and is now:

    Image

    And it's now redirecting (after clearing browser cache), and we're all done here!

  10. added a commit that references this issue on Aug 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions