Switching from trunk-based workflow #54
Replies: 2 comments 3 replies
-
|
A better way to solve this problem might be to just release more stuff like v0.2.0 and v0.3.0 for each PR that is successful. That and maybe include one of those quicklinks to the v0.1.1 docs. Sorta like this -ish: my github wiki action🙋♀️ my cool desc here usage📜 if you're looking for older version documentation, check out the old releases ☝ is that the kind of problem you're referring too? 🤔 |
Beta Was this translation helpful? Give feedback.
-
|
Yeah. I suppose the problem was that I was being lazy instead of making releases more quickly 😆 |
Beta Was this translation helpful? Give feedback.
-
|
If you really want to over engineer it you could make a GitHub action do it for you somehow 😜 |
Beta Was this translation helpful? Give feedback.
-
|
https://github.com/spenserblack/actions-wiki/releases/tag/v0.2.0 |
Beta Was this translation helpful? Give feedback.
-
|
Think I'll stick with trunk-based workflow after all. Closing. |
Beta Was this translation helpful? Give feedback.
-
Right now, the README is very out-of-date with the initial release, and can be confusing to users. This may continue to happen in the future. For this reason, I'm considering a development branch and a release branch. The release branch would be reverted to a much earlier commit, somewhere near the initial release.
Beta Was this translation helpful? Give feedback.
All reactions