-
-
Notifications
You must be signed in to change notification settings - Fork 368
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
[RFC] build --tag=staging #196
Labels
enhancement
New feature or request
Comments
louisgv
changed the title
[RFC] Staging or more deployment environment
[RFC] Staging or more deployment tag
Oct 4, 2022
louisgv
changed the title
[RFC] Staging or more deployment tag
[RFC] Staging or more build tag
Oct 4, 2022
Also the ability to build the development package would be nice |
Tagged build should:
|
louisgv
changed the title
[RFC] Staging or more build tag
[RFC] Staging or more build --tag
Oct 4, 2022
@louisgv regarding the tagged env file
We can have the same order for icons |
louisgv
added a commit
that referenced
this issue
Nov 5, 2022
* --tag implementation * revert utils * use app-specific flag map * remove unused import Co-authored-by: Louis <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How do you envision this feature/change to look/work like?
--staging="staging-tag" or by default it's just "staging"
What is the purpose of this change/feature? Why?
For cases where developers makes more deployment than just prod (staging, alpha, beta)
(OPTIONAL) Example implementations
No response
(OPTIONAL) Contact Details
No response
Verify canary release
plasmo
canary releaseCode of Conduct
The text was updated successfully, but these errors were encountered: