🚀 Feature: Add accessibility-alt-text-bot GitHub Actions workflow #825
Labels
status: accepting prs
Please, send a pull request to resolve this!
type: feature
New enhancement or request
Comments
JoshuaKGoldberg
added
type: feature
JoshuaKGoldberg
changed the title
JoshuaKGoldberg
added
status: blocked
|
Unblocked! 😄 |
|
Awesome, thanks @kendallgassner! To anybody interested in implementing this: please do 😄. That'd be great. I'll want to see examples of the bot in another repository that you've set up with the latest version of the bot. I'd suggest using this template to make a new repository. |
JoshuaKGoldberg
added
status: accepting prs
JoshuaKGoldberg
added a commit
that referenced
this issue
Oct 30, 2023
## PR Checklist - [X] Addresses an existing open issue: fixes #825 - [X] That issue was marked as [`status: accepting prs`](https://github.com/JoshuaKGoldberg/create-typescript-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22status%3A+accepting+prs%22) - [X] Steps in [CONTRIBUTING.md](https://github.com/JoshuaKGoldberg/create-typescript-app/blob/main/.github/CONTRIBUTING.md) were taken ## Overview This PR adds a new bot to check for alt text in issue, PR or discussion comments. With the .yml file, I followed the suggestion in the [official repo](https://github.com/github/accessibility-alt-text-bot) and adapted the used version to the latest version. --------- Co-authored-by: Josh Goldberg <[email protected]>
|
🎉 This is included in version v1.41.0 🎉 The release is available on: Cheers! 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report Checklist
mainbranch of the repository.Overview
This is fantastic. Both for accessibility and folks posting giant screenshots of code in issues (always a blurgh).
https://github.blog/2023-06-12-make-your-github-projects-more-accessible-with-accessibility-alt-text-bot
Additional Info
I believe this is blocked on github/accessibility-alt-text-bot#28 & github/accessibility-alt-text-bot#30, though.
The text was updated successfully, but these errors were encountered: