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

[Github] Use our own issue labeler fork #65900

Merged
merged 1 commit into from
Sep 15, 2023

Conversation

cor3ntin
Copy link
Contributor

@cor3ntin cor3ntin commented Sep 10, 2023

As discussed in #65701 (comment)
⚠️ llvm/actions#6 must be merged first

@cor3ntin cor3ntin requested a review from a team as a code owner September 10, 2023 14:19
@tstellar
Copy link
Collaborator

What is the difference between our fork and upstream?

@cor3ntin
Copy link
Contributor Author

What is the difference between our fork and upstream?

Copy link
Collaborator

@tru tru left a comment

Choose a reason for hiding this comment

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

LGTM

@MaskRay
Copy link
Member

MaskRay commented Sep 12, 2023

Consider a short summary even the description contains two links. My first intuition was also

What is the difference between our fork and upstream?

@cor3ntin cor3ntin merged commit 6c82430 into llvm:main Sep 15, 2023
3 checks passed
ZijunZhaoCCK pushed a commit to ZijunZhaoCCK/llvm-project that referenced this pull request Sep 19, 2023
- Only adds 'new issue' if no other label is added
(llvm#65701)

- No not add labels if labels were already set
- Only add `foo` if there are no `foo:bar` label being added (although,
we don't use that yet)

Fixes llvm#65701
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.

None yet

5 participants