notBdougie

• ClojureScript (project)
• "A Tool For Thought" (post)

developerayo

• DevRelChat (podcast)
• unStack Africa (community)
• Lazy Loading images progressively and bundle analyzing in Webpack (video)

Requirements for your Awesome list

• Has been around for at least 30 days.
  That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
• Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
• The default branch should be named main, not master.
• Includes a succinct description of the project/theme at the top of the readme. (Example)
  • ✅ Mobile operating system for Apple phones and tablets.
  • ✅ Prototyping interactive UI designs.
  • ❌ Resources and tools for iOS development.
  • ❌ Awesome Framer packages and tools.
    -[ ] It's the result of hard work and the best I could possibly produce.
    If you have not put in considerable effort into your list, your pull request will be immediately closed.
• The repo name of your list should be in lowercase slug format: awesome-name-of-list.
  • ✅ awesome-swift
  • ✅ awesome-web-typography
  • ❌ awesome-Swift
  • ❌ AwesomeWebTypography
• The heading title of your list should be in title case format: # Awesome Name of List.
  • ✅ # Awesome Swift
  • ✅ # Awesome Web Typography
  • ❌ # awesome-swift
  • ❌ # AwesomeSwift
• Non-generated Markdown file in a GitHub repo.
• The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
• Not a duplicate. Please search for existing submissions.
• Only has awesome items. Awesome lists are curations of the best, not everything.
• Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
• Includes a project logo/illustration whenever possible.
  • Either centered, fullwidth, or placed at the top-right of the readme. (Example)
  • The image should link to the project website or any relevant website.
  • The image should be high-DPI. Set it to maximum half the width of the original image.
• Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
• Includes the Awesome badge.
  • Should be placed on the right side of the readme heading.
    • Can be placed centered if the list has a centered graphics header.
  • Should link back to this list.
• Has a Table of Contents section.
  • Should be named Contents, not Table of Contents.
  • Should be the first section in the list.
  • Should only have one level of nested lists, preferably none.
• Has an appropriate license.
  • We strongly recommend the CC0 license, but any Creative Commons license will work.
    • Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=master&template=cc0-1.0 (replace <user> and <repo> accordingly).
  • A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
  • Place a file named license or LICENSE in the repo root with the license text.
  • Do not add the license name or text to the readme. GitHub already shows the license name at the top of the repo.
  • To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.
• Has contribution guidelines.
  • The file should be named contributing.md. Casing is up to you.
• Has consistent formatting and proper spelling/grammar.
  • The link and description are separated by a dash.
    Example: - [AVA](…) - JavaScript test runner.
  • The description starts with an uppercase character and ends with a period.
  • Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
• Doesn't include a Travis badge.
  You can still use Travis for list linting, but the badge has no value in the readme.
• Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

lwgray

• "Yellowbrick: Machine Learning Visualization (project)

handle

• "Link 1 Description" (video/slides/post/interview/project/community)
• "Link 2 Description" (video/slides/post/interview/project/community)

lipemorais

• AfroPython (community)
• "The world is more than we can see with our lenses" (blog)
• "AfroPython: Empowering black people using Python in Brazi" (video)
• "How to receive feedback" (blog)

notBdougie

• "Link 1 Description" (video/slides/post/interview/project/community)
• "Link 2 Description" (video/slides/post/interview/project/community)

torch2424

• "wasmboy" (project)
• "assemblyscript" (project)

kjaymiller

• Productivity in Tech (project)
• PIT Reflection: GitHub Sponsors, Talking to Mentors, and Writing Docs (podcast)

At the moment I am using an action to print the markdown for developers into the logs and copy and pasting that into markdown.

Make it better

• Move the array of developers out of update-photos.rb and into its own file
• Have the action print the new photos to a file or directly in the readme through automation.
• Update the CONTRIBUTING.md to reflect the above changes.

swannodette

• ClojureScript (project)
• "A Tool For Thought" (post)

imolorhe

• ✨⚡️ A beautiful feature-rich GraphQL Client for all platforms. (project)

ThePhD

• "Transcoding Support in C" (post)
• sol2 (project)

bcdbuddy

• "Website" (http://babacar-cisse-dia.com/)
• "Dev.to" (profile)

brandonroberts

• "ngrx/platform maintainer" (project)
• "Angular Unfiltered" (podcast)

https://github.com/bdougie/awesome-black-developers/tree/main/.github/workflows

if: startsWith(${{ github.event.issue.title }}, "Add handle")

should be

if: startsWith( "Add handle", ${{ github.event.issue.title }})