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

Build docs for Python changes #7819

Merged
merged 1 commit into from Feb 22, 2024
Merged

Conversation

nulano
Copy link
Contributor

@nulano nulano commented Feb 20, 2024

Also run the docs workflow when Python files are updated, as this can affect Documentation if e.g. type hints are changed. This could have prevented issues such as what caused #7812.

@radarhere
Copy link
Member

I feel like it would be almost the same, and easier, to just build the docs every time?

@nulano
Copy link
Contributor Author

nulano commented Feb 20, 2024

I feel like it would be almost the same, and easier, to just build the docs every time?

Sure, that is what I was considering initially, but perhaps it's not necessary to rebuild docs when adding type hints to tests (e.g. #7816) or updating dependencies (e.g. #7752).

I don't have a strong preference either way, this just seems simpler to me.

@hugovk
Copy link
Member

hugovk commented Feb 21, 2024

Looks good!

@nulano Thanks again for all your help triaging issues and reviewing PRs! Can we add you as a triager to this repo? It means you can label PRs yourself, and also close/re-open issues/PRs (for example, closing as duplicate). You could also join our Discord/Slack. What do you think? :)

@radarhere radarhere merged commit b8722f3 into python-pillow:main Feb 22, 2024
6 of 8 checks passed
@nulano
Copy link
Contributor Author

nulano commented Mar 2, 2024

Can we add you as a triager to this repo? It means you can label PRs yourself, and also close/re-open issues/PRs (for example, closing as duplicate).

Sure, we could give that a go. :)

You could also join our Discord/Slack. What do you think? :)

Feel free to send me an invite; I should have the same username on Discord, but don't actively use it.

@nulano nulano deleted the docs-all branch March 2, 2024 22:34
@hugovk
Copy link
Member

hugovk commented Mar 3, 2024

Great, Discord/Slack invites sent!

@aclark4life I don't have access: please could you create a triage team for https://github.com/python-pillow and add @nulano?

https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization

@nulano
Copy link
Contributor Author

nulano commented Mar 3, 2024

Great, Discord/Slack invites sent!

Hmm, I don't see anything. Did Discord/Slack ask for an email address to send the invite? My email server's boot drive just died yesterday so I won't be able to receive email for a few days on the email address I use on GitHub (GitHub invite should be fine - I've temporarily changed my GitHub notification address to use my private email). I'll let you know when I've got it fixed.

@aclark4life
Copy link
Member

@nulano @hugovk Done!

Screenshot 2024-03-03 at 1 46 18 PM

@nulano
Copy link
Contributor Author

nulano commented Mar 3, 2024

And accepted!

image


It means you can label PRs yourself, and also close/re-open issues/PRs (for example, closing as duplicate).

But I don't see any changes in the GitHub interface, e.g. I still can't see an edit labels button on this PR like I can in projects in other organizations.

@hugovk
Copy link
Member

hugovk commented Mar 4, 2024

I sent invite links from my email to the email address on your GitHub profile. I've also sent a friend request on Discord, I don't think it's possible to invite someone directly who's "unknown".

@hugovk
Copy link
Member

hugovk commented Mar 4, 2024

@aclark4life Did you also give triage role/permission to the team?

@aclark4life
Copy link
Member

@aclark4life Did you also give triage role/permission to the team?

No, I clicked around a bit and couldn't find out where/how to do that, at which point I got generally confused about GitHub's roles/teams/people/permissions/sigh. Then I remembered in the early days they made some major change to that system and I don't think I've understood what's going on since then 🤔

Annoyingly, nothing happens when I go here except I can filter stuff.

Screenshot 2024-03-04 at 5 43 08 AM

Sooo… we need to find where/how to give triage/role permission and the only explanation for the missing configuration option I can think of is … we need enterprise? 🤷

@hugovk
Copy link
Member

hugovk commented Mar 4, 2024

We don't need enterprise. I think we need to add the team to the repo:

Add triage team to a repo: https://github.com/python-pillow/Pillow/settings/access -> Add team -> Enter "Triage" -> Choose a role -> Triage

@aclark4life
Copy link
Member

Done!

Screenshot 2024-03-04 at 8 46 34 AM

@nulano nulano added the Testing label Mar 4, 2024
@nulano
Copy link
Contributor Author

nulano commented Mar 4, 2024

Looks like that worked!

@hugovk
Copy link
Member

hugovk commented Mar 4, 2024

Welcome to the team! 🚀

@nulano
Copy link
Contributor Author

nulano commented Apr 3, 2024

I sent invite links from my email to the email address on your GitHub profile. I've also sent a friend request on Discord, I don't think it's possible to invite someone directly who's "unknown".

I didn't see the friend request when I checked earlier, but I just found and accepted it.


My email server's boot drive just died yesterday so I won't be able to receive email for a few days on the email address I use on GitHub. [...] I'll let you know when I've got it fixed.

I could get the email server running again with my new boot drive, but unfortunately I didn't have a backup of the email server config (among others) and I'm still waiting for a quote on data recovery (I was supposed to receive it by now) to find out whether I have to redo it. :/

@hugovk
Copy link
Member

hugovk commented Apr 4, 2024

My email eventually bounced because it couldn't reach the server, but I've sent fresh invites via Discord 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants