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

update github action & semantic-release for channel distribution #1771

Open
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

RingoTC
Copy link
Contributor

@RingoTC RingoTC commented Mar 4, 2024

Description

comment:
Update Github Action configuration and semantic-release configuration for channel distribution. #1762

  • branches leading with feature/ will deploy to the alpha channel
  • branches leading with bugfix/ and test/ will deploy to the beta channel
  • the main branch will deploy to the prod channel

Type of change

  • New feature (non-breaking change which adds functionality)

.releaserc.json Outdated
@@ -21,9 +21,19 @@
"channel": "next"
},
{
"name": "demo",
"name": "feature/**",
Copy link
Collaborator

Choose a reason for hiding this comment

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

Does the semantic release accept wide matching? Do you have any document or example for this? I don't know if it does.

@RingoTC
Copy link
Contributor Author

RingoTC commented Mar 5, 2024

Yes, actually the wide matching is implemented by the GitHub action workflow configuration.

For example, when we make a push with branch name like "feature/test4semantic", then the dev distribution will trigger only.

image

And I think the real purpose of semantic-release is to generate version documentation automatically and push the patch to package management site like npm. So we can only change the workflow configuration to achieve our purpose that select different workflow process depends on the branch name.

@dadiorchen
Copy link
Collaborator

Yea, github action support the wide matching, but seems the semantic release lib doesn't so it can not trigger the thing for real branch like feature/1

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.

3 participants