--- Log opened Thu Oct 07 00:00:41 2021 |
00:17 | | Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has quit [Connection closed] |
02:58 | | macdjord [macdjord@Nightstar-7aijs7.dsl.bell.ca] has quit [Connection closed] |
02:58 | | macdjord [macdjord@Nightstar-7aijs7.dsl.bell.ca] has joined #code |
02:58 | | mode/#code [+o macdjord] by ChanServ |
04:00 | | Degi_ [Degi@Nightstar-fsdf6h.pool.telefonica.de] has joined #code |
04:01 | | Degi [Degi@Nightstar-dt2neu.dyn.telefonica.de] has quit [Operation timed out] |
04:01 | | Degi_ is now known as Degi |
04:37 | <@sshine> | I've been stuck at this for a while: I want to use tags on github to trigger releases. but I also want releases to be reviewed. a PR cannot add tags, since a tag is just a git ref, and a PR merges a feature branch (just another ref) onto whatever branch, e.g. the main branch. |
04:38 | <@sshine> | some colleagues on another team use a Slack bot with git commit access to add the tags. but I don't like to do chat-based releases, I want to do peer-reviwed ones. |
04:38 | <@sshine> | I've set up branch-based releases, e.g. having a branch called 'release/production' and merging onto that triggers a deployment. |
05:20 | <&McMartin> | I've only seen this stuff managed by external processes that gate the commits to the github stuff |
05:21 | <&McMartin> | Like, this seems like a job for something more like TeamCity than GH itself |
05:23 | <&McMartin> | (TC is the only system like this I have any real experience with; I can't vouch for it as better than its competitors or anything) |
05:33 | | VirusJTG [VirusJTG@Nightstar-b00.oti.104.208.IP] has quit [Connection closed] |
05:33 | | VirusJTG [VirusJTG@Nightstar-b00.oti.104.208.IP] has joined #code |
05:33 | | mode/#code [+ao VirusJTG VirusJTG] by ChanServ |
05:44 | <@sshine> | McMartin, okay. so you've seen tag-based release systems, but the tags were added and pushed by an external system. |
06:16 | <&McMartin> | Yeah, something that gets notified when commits happen or when they happen with special messages or stuff in the PR that have instructions to it, etc |
06:20 | <&McMartin> | That said: I am Extremely Not Ops, and my ignorance of this stuff is pretty vast. There may be standard solutions for this I've never encountered, because I normally wouldn't. |
08:40 | <&McMartin> | Welp, took me three weeks to put together what was supposed to just be a tiny sidebar, but it's done |
08:40 | <&McMartin> | https://bumbershootsoft.wordpress.com/2021/10/07/interlude-resource-systems/ |
08:48 | | Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has joined #code |
08:48 | | mode/#code [+qo Vornicus Vornicus] by ChanServ |
09:09 | | Alek [Alek@Nightstar-06ca3p.il.comcast.net] has quit [Ping timeout: 121 seconds] |
09:12 | | Alek [Alek@Nightstar-06ca3p.il.comcast.net] has joined #code |
09:14 | | catalyst_ is now known as catalyst |
10:20 | | Kindamoody is now known as Kindamoody|afk |
11:17 | | JustBob [justbob@Nightstar.Customer.Dissatisfaction.Administrator] has quit [Operation timed out] |
11:18 | | JustBob [justbob@ServerAdministrator.Nightstar.Net] has joined #code |
11:18 | | mode/#code [+o JustBob] by ChanServ |
17:17 | | Emmy [Emmy@Nightstar-l49opt.fixed.kpn.net] has joined #code |
19:40 | | catalyst_ [catalyst@Nightstar-hg0ofp.dab.02.net] has joined #code |
19:43 | | catalyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has quit [Ping timeout: 121 seconds] |
21:09 | | catalyst [catalyst@Nightstar-hg0ofp.dab.02.net] has joined #code |
21:11 | | catalyst_ [catalyst@Nightstar-hg0ofp.dab.02.net] has quit [Ping timeout: 121 seconds] |
21:18 | | abudhabi [abudhabi@Nightstar-mjmojr.adsl.tpnet.pl] has quit [Ping timeout: 121 seconds] |
21:18 | | abudhabi [abudhabi@Nightstar-ncfldm.adsl.tpnet.pl] has joined #code |
22:05 | | Kindamoody|afk is now known as Kindamoody |
22:28 | | catalyst_ [catalyst@Nightstar-ejd4sd.cable.virginm.net] has joined #code |
22:31 | | catalyst [catalyst@Nightstar-hg0ofp.dab.02.net] has quit [Connection closed] |
23:25 | | Emmy [Emmy@Nightstar-l49opt.fixed.kpn.net] has quit [Ping timeout: 121 seconds] |
23:41 | <&ToxicFrog> | It's not a "data breach", it's a "surprise distributed backup" |
23:51 | <@TheWatcher> | Pfft |
--- Log closed Fri Oct 08 00:00:43 2021 |