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

chore: include publish workflow #74

Closed
alestiago opened this issue Feb 28, 2024 · 1 comment · Fixed by #124
Closed

chore: include publish workflow #74

alestiago opened this issue Feb 28, 2024 · 1 comment · Fixed by #124
Assignees
Labels
chore Changes that don't modify source code or tests p1 High-priority issues at the top of the work list

Comments

@alestiago
Copy link
Contributor

alestiago commented Feb 28, 2024

Description

We should include a workflow that when triggered by a new tag, it publishes the templates.

Since mason still suffers from felangel/mason#781, publishing locally might include ephemeral files, whereas publishing from a workflow ensures no undesired files like ".DS_Store" are bundled when publishing locally using the mason_cli.

In addition, having a publishing workflow might streamline the delivery and work associated with a release.

@alestiago alestiago added chore Changes that don't modify source code or tests needs triage Issue requires triage labels Feb 28, 2024
@tomarra tomarra added p2 Important issues not at the top of the work list and removed needs triage Issue requires triage labels Mar 12, 2024
@tomarra tomarra added p1 High-priority issues at the top of the work list and removed p2 Important issues not at the top of the work list labels Jun 4, 2024
@alestiago
Copy link
Contributor Author

Moving this to blocked until VeryGoodOpenSource/very_good_workflows#194 gets resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Changes that don't modify source code or tests p1 High-priority issues at the top of the work list
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants