-
Notifications
You must be signed in to change notification settings - Fork 252
Add GitHub Actions workflow file option #188
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
base: main
Are you sure you want to change the base?
Conversation
9f02882 to
ff8c320
Compare
ff8c320 to
e47b9aa
Compare
|
@joaomoreno You know more about CI scripts than me: If you could review, that would be great! |
|
Sorry @aeschli I really don't know much about GH Actions. This looks like a cool addition though! |
|
@joaomoreno @aeschli any interest in this still? It would be great to include scaffolding to help with steps to publish an extension. I started down a path in creating my own template GitHub repository that includes pieces to cover that so I don't have to keep doing it manually. When I shared it more publicly it was suggested to look into including it in the generator which lead me to finding this PR :) |
Tjolk-072
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work, thank you very much.
Tjolk-072
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work, thank you very much.
Tjolk-072
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work, thank you very much.
I was inspired by #165 to add a basic GitHub Actions workflow file.
This change adds a new option asking if a Github workflow file should be included.
The included workflow will test on all pushes, and publish on release (git tag), for the following types:
The included workflow will just publish on release (git tag), for the following types:
The extension author then just needs to then add
AZURE_TOKENas a secret.View an example workflow run here: https://github.com/badsyntax/vscode-generator-eslint-prettier-example/commit/83533b0082a00ffa91b91cd985f62739a5a2131a/checks?check_suite_id=349694101