Project workflows insufficiently documented

[keikoro]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

GitHub Issues/Projects/Automating projects/Using built-in automations

What part(s) of the article would you like to see updated?

The built-in project workflows aren't fully/properly documented.

The Using built-in automations page should list all currently available workflows (and their limitations) or have a new sub page added to it which describes them all.

I personally only ever discover new or improved project workflows by chance because once workflows are configured for a project, they rarely need checking/reviewing/changing.

Additional information

Tangentially related: the fact this repo doesn't have a separate label for projects kinda confirms my overall impression that projects are a somewhat neglected feature of GitHub.

[welcome]

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[Sharra-writes]

@keikoro Thanks for opening an issue about this! Let me look into it and see if there's interest internally in expanding some of the documentation. I think you're right that, in an ideal world, the available workflows would be listed with, perhaps, some examples of when and how to use them. The Docs team is small and we can't do everything, but we might be able to enlist some support on this. I won't know without asking! ✨

[Sharra-writes]

@keikoro I talked to the team, and we unfortunately don't have the bandwidth to address this right now. Even verifying something written by an outside contributor would be beyond our capacity at the moment, so I'm going to have to close this one. I'm sorry. I will see about getting a label for projects in this repo, at least. It's not much, but at least we can get things labeled better.