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.

Sign up for GitHub

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

Jump to bottom

TEST PLEASE IGNORE: test ofborg bsd labelling #164504

Closed
wants to merge 1 commit into from
Closed

TEST PLEASE IGNORE: test ofborg bsd labelling #164504

wants to merge 1 commit into from

Conversation

cole-h
Copy link
Member

@cole-h cole-h commented Mar 16, 2022

Testing NixOS/ofborg#573.

@ofborg ofborg bot added the 6.topic: bsd Running or building packages on BSD label Mar 16, 2022
@cole-h
Copy link
Member Author

cole-h commented Mar 16, 2022

Nice, exactly what I was hoping for :)

@cole-h cole-h closed this Mar 16, 2022
@cole-h cole-h deleted the ofborg-test branch March 16, 2022 22:24
@github-actions github-actions bot removed the 6.topic: bsd Running or building packages on BSD label Mar 16, 2022
@zowoq
Copy link
Contributor

zowoq commented Mar 16, 2022

nixpkgs/.github/labeler.yml

Lines 8 to 10 in 0395086

"6.topic: bsd":
- pkgs/os-specific/bsd/**/*
- pkgs/stdenv/freebsd/**/*

Need to remove this, can't have a label that is managed by both.

@cole-h
Copy link
Member Author

cole-h commented Mar 16, 2022 •
edited

Is there no way for them to both work? It would be nice to allow the e.g. bsd label based on title or file path.

@cole-h
Copy link
Member Author

cole-h commented Mar 16, 2022 •
edited

Looks like we might be able to use this workaround:

actions/labeler#112 (comment)

(specifically: setting sync-labels to the empty YAML string '')

WDYT?

@cole-h cole-h mentioned this pull request Mar 17, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
10.rebuild-darwin: 0 10.rebuild-linux: 0
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@cole-h @zowoq