Publish a new workflow for duplicating mirror image at brainstormforce/bsf-admin-ui#388
Merged
imnavanath merged 10 commits intomasterfrom Feb 9, 2026
Merged
Publish a new workflow for duplicating mirror image at brainstormforce/bsf-admin-ui#388imnavanath merged 10 commits intomasterfrom
imnavanath merged 10 commits intomasterfrom
Conversation
Add a GitHub Actions workflow (.github/workflows/publish.yml) to publish the package on release events using Node 18, running npm ci, build, and npm publish with NODE_AUTH_TOKEN. Update package.json to set publishConfig.registry to GitHub Packages and correct the repository URL to brainstormforce/force-ui so the package is published to the @brainstormforce scope.
Update package.json to change the npm package scope/name from @bsf/force-ui to @brainstormforce/force-ui to reflect organization branding. No other fields or version were modified.
Introduce .editorconfig to standardize editor/IDE formatting and whitespace rules. Add a GitHub Actions workflow (publish-public-build.yml) that runs on pushes to the publish-workflow branch, builds the project with Node 18, and pushes the generated dist and bumped package.json to a public mirror repo (commits and tags the release). Update package.json publishConfig to include "access": "restricted" for the npm registry.
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| { | ||
| "name": "@bsf/force-ui", | ||
| "name": "@brainstormforce/force-ui", | ||
| "version": "1.7.7", |
There was a problem hiding this comment.
What: The addition of the 'publishConfig' section specifies the GitHub Packages registry and sets access to restricted, which is great for managing package visibility.
Why: This change helps prevent unauthorized access to your packages and ensures that only intended users can install or publish to this repository.
How: Make sure that any environment variable/configuration to authenticate with GitHub Packages is properly handled in your CI/CD pipeline, as this is critical for the automation of package publishing.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This pull request introduces several improvements to the repository's configuration and publishing workflows. The main changes include adding automated GitHub Actions workflows for publishing builds and packages, updating the package configuration for proper publishing to GitHub Packages, and standardizing code style across editors.
Build & Publish Automation:
.github/workflows/publish-public-build.yml) to automate building the project and pushing build artifacts to a public mirror repository when a release is created..github/workflows/publish.yml) to automate publishing the package to GitHub Packages when changes are pushed to thepublish-workflowbranch.Package Configuration Updates:
package.jsonto@brainstormforce/force-uiand set the repository URL to the correct organization and repository. [1] [2]publishConfigsection topackage.jsonto specify the GitHub Packages registry and set access to restricted.Editor Configuration:
.editorconfigfile to enforce consistent coding styles and indentation across different editors and file types.Screenshots | Video with voice-over
Link to Figma (If applicable)
How has this been tested?
Checklist: