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

Fix build_file labels #1425

Merged
merged 2 commits into from
Oct 22, 2024
Merged

Fix build_file labels #1425

merged 2 commits into from
Oct 22, 2024

Conversation

brentleyjones
Copy link
Collaborator

Regressed for WORKSPACE users in 7fafc9b.

Copy link
Contributor

@mattrobmattrob mattrobmattrob left a comment

Choose a reason for hiding this comment

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

Is it worth adding a simple test to existing CI to make sure this doesn't become broken again? Assuming we're supporting WORKSPACE in the next breaking changes release.

@brentleyjones
Copy link
Collaborator Author

We would have to have another workspace that loads this one, since it the labels do resolve correctly from within the repo. I think that's too much hassle for something that shouldn't really break again. And yeah, I'm not 100% sure we will support WORKSPACE in rules_swift 3.0.

Regressed for WORKSPACE users in 7fafc9b.

Signed-off-by: Brentley Jones <github@brentleyjones.com>
Signed-off-by: Brentley Jones <github@brentleyjones.com>
@brentleyjones brentleyjones force-pushed the bj/fix-build_file-labels branch from de50737 to 3859dd9 Compare October 22, 2024 13:16
@mattrobmattrob
Copy link
Contributor

Sounds good to me

@brentleyjones brentleyjones merged commit e831c3a into master Oct 22, 2024
12 checks passed
@brentleyjones brentleyjones deleted the bj/fix-build_file-labels branch October 22, 2024 13:18
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