Is this maintained?

[ichard26]

Hi there 👋

The master version is getting stuck at psf/black@cac182. This is a problem since people are submitting bug reports under the impression their bug exists on master when in fact it might not (it's actually how I discovered this issue). This is going to get worse with time, especially since we're releasing a hotfix version for 21.4b0 and then updating the stable ref very soon.

I totally understand if you can't keep this functional anymore (it's not like you're getting paid for this anyway!), I'd just like to know whether we should expect this to become functional again.

Regardless, thank you so much for all of your work in keeping this functional over the years! I'm sure it's been a great help to the Black community.

[jpadilla]

@ichard26 ahhh sorry about that! I just noticed that travisci disabled the builds. I'll try to unblock now, and move things to GitHub Actions.

[jpadilla]

@ichard26 just updated manually, I'll work on moving to GitHub Actions next.

[ichard26]

@jpadilla thank you so much! It's highly appreciated :)

[jpadilla]

should be all set now 😄

[ichard26]

Thanks! 🖤

p.s.

black-playground/.github/workflows/deploy.yml

Lines 44 to 51 in 37f453d

	- name: "Deploy stable"
	env:
	AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
	AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
	run: |
	cd api
	pipenv install git+https://github.com/ambv/black.git#egg=black
	bin/deploy master

The step's name should be probably be "Deploy master". Also while ambv/black does redirect to psf/black, it probably would be safer to just reference psf/black directly (you can make that change while fixing the name :) )