Use the GitHub API to get the label's node ID

[dhruvkb]

Description

@sarayourfriend was right in this review, I should've used an API to get the label IDs instead of hardcoding them. Using hardcoded labels would mean that the infrastructure repo labelling would not work as those IDs were from the monorepo and only present on the monorepo.

This PR is not critical though as labelling works on the monorepo for now and the infra repo is private and only accessible to maintainers who can label their own PRs till this is merged and pushed.

Checklist

• My pull request has a descriptive title (not a vague title likeUpdate index.md).
• My pull request targets the default branch of the repository (main) or a parent feature branch.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added or updated tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no visible errors.
• I ran the DAG documentation generator (if applicable).

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[sarayourfriend]

Interesting problem, that problem hadn't crossed my mind. Thinking of the API limits issue. I wonder if it's possible to consolidate any queries? I haven't looked at the workflow at all to see for myself, but I can help look later if you'd like. Maybe GraphQL Fragments would be viable for it?

[dhruvkb]

Yes @sarayourfriend I would appreciate any audit into where we could avoid or consolidate API calls. GraphQL might not be 100% helpful because GitHub calculates GraphQL rate limits differently rather than number of calls which applies to REST.

[obulat]

We could also have 2 hard-coded options and select one of them based on the repository where this runs to prevent extra GitHub API calls.

[dhruvkb]

That's such a simple idea @obulat, and so elegant as well. We will definitely do that once we start getting rate-limited by GitHub. Till then the more flexible it is, the better 👍!