Closed gobengo closed 6 years ago
@gobengo I'm pretty sure this will keep failing on Travis while this branch is on your fork. Can you push to sudomesh:travis-tags and reopen?
https://docs.travis-ci.com/user/pull-requests/#Pull-Requests-and-Security-Restrictions
I did not repush, but I made the build pass in sudomesh org.
Sorry I missed this @gobengo . I don't think I totally understand what this PR does. Would you be up for chatting online or in person about it?
Yep. Let's put on agenda for 6/20 software WG meeting (a general discussion on bug 34 perhaps).
Helping my mom move through the end of the week in Poland but I'll watch for you on chat when in online to discuss sooner.
On Mon, Jun 11, 2018, 10:57 AM Benny Lichtner notifications@github.com wrote:
Sorry I missed this @gobengo https://github.com/gobengo . I don't think I totally understand what this PR does. Would you be up for chatting online or in person about it?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/sudomesh/monitor/pull/23#issuecomment-396171706, or mute the thread https://github.com/notifications/unsubscribe-auth/AAKfBiEFoiy6VT8OGCIOyOm_zJl74j_3ks5t7jDqgaJpZM4T-Swn .
Yep. Let's put on agenda for 6/20 software WG meeting (a general discussion on bug 34 perhaps).
Sounds great! Would be 6/19 I think? The tuesday?
Helping my mom move through the end of the week in Poland but I'll watch for you on chat when in online to discuss sooner.
Kk. Good luck with the move!! Bring back Polish treats? :yum:
@bennlich treats procured
Bennie and I just synced on this work. I think everyone involves agrees that while the workflow changes may be appropriate for more critical components like sudowrt-firmware, they are overkill for this repo. I'm closing this issue, but may re-propose a similar one for sudowrt-firmware.
This is an automated way of managing git tags (a.k.a. releases) in an automated way using GitHub conventions.
This PR establishes a new + automated release workflow
package.json
version number does not correspond to an exissting git tag. i.e. you need to increment package.json version number to an unreleased version in order to start devving new features.What this enables:
New build functionality