Doot-doot-doo... commitin' code directly to master 'cause everyone else on my team's out today....
BIAS THIS FOR ACTION, DEVVERS! :middle_finger_clw_b2:
(( Under ninety-nine percent of circumstances, this is a terrible move, but there's nobody around who can tell me if my code's good and I can only really test it if it's in staging. I've validated my rollback plan and prod is disconnected in my pipeline. I may take a cavalier attitude at times but I'm still a professional. ))
@literorrery Your staging environment runs on the master branch?
...D:
@mawr We have a full CI/CD setup. Everything runs on the master branch but is gated for release based on tags. It's so we can push as much crap as we like to side branches but only master-merges get auto-promoted from GitHub to our staging environment. This app doesn't have a full dev environment because of the nature of the project.
@literorrery I just imagined you doing that and comically everything around you just immediately catches fire and alarms blare
@Oneironott That would validate that my monitors are working! =n.n=
@literorrery suuuure you don't have any coyote in you :P
@Oneironott It's not _coyote_, but there is trickster. =>.>=
@literorrery ahaa :P Everyone needs a little trickster, I think n.n
And what do you know, it did go awry. Not terrible, just committed to the wrong repo. Ha ha. Time to validate that rollback plan....