The Bridge

« first day (4656 days earlier) ← previous day next day → last day (679 days later) »

SPArcheon

07:51

Still have to check but apparently a few hours ago the console patch for Binding of Isaac finally dropped.

Last one was more than a year ago

SPArcheon

08:15

Last console patch was probably the equivalent of 1.7.8 on PC (yep, they are stupid enough to use different numbers)

3 hours later…

bwDraco

10:58

Apr 3 at 0:47, by murgatroid99

My experience was that modified starter decks got me up to Silver, or maybe Gold, but then I needed a stronger deck to get past that.

@murgatroid99 Managed to get to Platinum 4 using a Gruul werewolf deck that was heavily modified from the stock On the Hunt deck. It's still a bit janky, but I've done a lot of work to make it more reliable.

I don't expect to get much further, though.

(24 rares, 4 mythic rares)

4 hours later…

MBraedley

14:58

@SaintWacko I was about to add an answer to this because I saw Azure DevOps and didn't realize you were talking about GitHub. Weird that they haven't implemented similar branch policies stuff for GitHub.

2 hours later…

SaintWacko

16:36

@MBraedley Right? Really annoying that you have to do it per repo

Fredy31

@SPArcheon Kinda impressed that you havent bailed on that version by now and just bought it on steam

Isaac must me kinda cheap by now

Shit, publisher on steam is your favorite, Nicalis. steamdb.info/app/250900

And still, 60$ store.steampowered.com/bundle/2405/…

ave

17:07

steamdb.info/bundle/2405 -88.75% on TRY

so glad I didn't change my region on steam yet

MBraedley

17:20

@SaintWacko wait, isn't it just this?

SPArcheon

@Fredy31 Nicalis on every platform. Furthermore, I mostly play on console only to save me the annoyance of a) hardware incompatibilities, b) stupid DRM or trash accounts system (see: EA)

ave

@MBraedley protected branches with limited set of approvers is going to require you add a CODEOWNERS file and require a review from code owners on your protected branch settings.

https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-pull-request-reviews-before-merging
> Optionally, you can choose to require reviews from code owners. If you do, any pull request that affects code with a code owner must be approved by that code owner before the pull request can be merged into the protected branch.

this is also the solution saintwacko found

MBraedley

17:35

Yeah, that article doesn't say anything on how to set the code owners. In Azure DevOps, you can set group(s) and/or individual(s) as required reviewers per branch.

Fredy31

Guess there is esports of anything. twitter.com/JakeSucky/status/…

SaintWacko

18:12

@MBraedley so you can protect branches and require approving pull requests, but the approvers list goes by a role of write or higher. So you can't set someone to have the ability to write to branches in the repo, but not be able to approve PRs into prod

SPArcheon

18:25

looks left...

looks right...