You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As @amiq11 suggested in the mailing list, I propose to use CI for auto deploy.
We should do the following 3 steps (testing/packaging/launching) AUTOMATICALLY
The triggers of them are different
a. testing occurs after pushing any change [DONE]
b. packaging occurs after merging (develop -> master)
c. launching occurs after making a release branch
As for this branch, launching means making a release and 2.b and 2.c can be done at once?
The text was updated successfully, but these errors were encountered:
I cleaned up the comments on #21 and now I want to make a new release. What do you think about this proposal? I really appreciate if you help me with this.
resolves#20.
This PR introduces a feature of auto deploy.
Procedure
1. Merge changes into `master` (e.g., `git checkout master; git merge develop`)
1. Make a tag (e.g., `git tag v2.2.0`)
1. Push changes (`git push --follow-tags`)
Note
I specify the format of a tag for deploy to `^v[0-9].*$` and added a feature removing the prefix `v` in the deploy task to follow the current naming rule of release folders.
As @amiq11 suggested in the mailing list, I propose to use CI for auto deploy.
As for this branch,
launching
means making a release and 2.b and 2.c can be done at once?The text was updated successfully, but these errors were encountered: