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

Avoid duplicate build folder in @primer/octicons #1001

Closed
wants to merge 1 commit into from

Conversation

fregante
Copy link
Contributor

In my local tests, running yarn build in lib/octicons_node generates build/build/svg but after this change it generates build/svg, so it should fix the issue.

However the build is a bit of spaghetti between workflows, docker entrypoints.js and multiple package.json, so it's not entirely clear if further work is required (probably not)

@fregante fregante requested a review from a team as a code owner December 20, 2023 03:15
@fregante fregante requested a review from tallys December 20, 2023 03:15
Copy link

changeset-bot bot commented Dec 20, 2023

⚠️ No Changeset found

Latest commit: 5750be4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@@ -17,7 +17,7 @@
"url": "https://github.com/primer/octicons/issues"
},
"scripts": {
"build": "\\cp -r ../build/ ./build && \\cp index.scss ./build/build.css",
"build": "\\cp -r ../build/. ./build && \\cp index.scss ./build/build.css",
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@broccolinisoup broccolinisoup requested a review from a team January 11, 2024 22:56
Copy link
Contributor

Hi! This pull request has been marked as stale because it has been open with no activity for 60 days. You can comment on the pull request or remove the stale label to keep it open. If you do nothing, this pull request will be closed in 7 days.

@github-actions github-actions bot added the Stale label Mar 11, 2024
@fregante
Copy link
Contributor Author

@broccolinisoup ☺️

@github-actions github-actions bot removed the Stale label Mar 12, 2024
Copy link
Contributor

@camertron camertron left a comment

Choose a reason for hiding this comment

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

Nice, thank you!

@camertron
Copy link
Contributor

camertron commented Mar 12, 2024

I'm not sure what's going on with these build failures, but I assume it's because this PR was created from a fork. I just pushed a copy up to origin to see if that fixes things: #1010

@camertron
Copy link
Contributor

camertron commented Mar 12, 2024

Merged in #1010

@camertron camertron closed this Mar 12, 2024
@fregante fregante deleted the patch-1 branch March 12, 2024 22:27
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.

[Feedback] npm package contains duplicate icon data
2 participants