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

ci: fix update-project workflow #192

Merged
merged 1 commit into from
May 29, 2024
Merged

Conversation

FFY00
Copy link
Member

@FFY00 FFY00 commented May 26, 2024

Successful example: FFY00/test-label-mapping#4

Successfull example:
FFY00/test-label-mapping#4

Signed-off-by: Filipe Laíns <[email protected]>
@lwasser
Copy link
Member

lwasser commented May 29, 2024

@FFY00 thank you for this! let's see how this runs here. it seems to be working perfectly in your linked example above!

@lwasser lwasser merged commit 740caa4 into pyOpenSci:main May 29, 2024
2 checks passed
@lwasser
Copy link
Member

lwasser commented May 29, 2024

@FFY00 i'm just catching up after pycon. id love to invite you to our pyOpenSci slack if you have bandwidth. You can also say "no thank you" if you are on too many chat platforms!!

@lwasser
Copy link
Member

lwasser commented May 29, 2024

@FFY00 this worked!! i had to fix the token scope but then it ran. there is one small thing. can you help me understand how it maps label to "status" on the board?

i just tested it on "0/pre-review-checks": and it moved to project board status: under-review. it should have moved it to pre-review-checks.

THANK YOU for getting this to work! i've been trying to implement this for a long time!

@FFY00
Copy link
Member Author

FFY00 commented May 29, 2024

@FFY00 i'm just catching up after pycon. id love to invite you to our pyOpenSci slack if you have bandwidth. You can also say "no thank you" if you are on too many chat platforms!!

Yeah, sure, just send me the link.

@FFY00
Copy link
Member Author

FFY00 commented May 29, 2024

there is one small thing. can you help me understand how it maps label to "status" on the board?

That's the field ID (PVTSSF_lADOAbmP7s4ASqjLzgL66FI). I didn't implement lookup from name to keep things simple, but I did include a query-project-by-number.gql query file to help update this if ever needed. I'd recommend you to run it, it should help clarify things for you.

gh api graphql --paginate --slurp -f query="$(cat query-project-by-number.gql)" -F org=pyOpenSci -F number=7

Ideally, we'd have a better solution where we don't have to hardcode the IDs, but I think for now it's fine. I would have already published some code to do that in a new action if it wasn't such a PITA to test.

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

Successfully merging this pull request may close these issues.

2 participants