Allow configuring Dependency Dashboard to be a "pinned issue"

[jamietanna]

Tell us more.

On some repositories, we want to have our Dependency Dashboard pinned to the repository's issues panel.

For instance on https://github.com/oapi-codegen/oapi-codegen/issues:

However, sometimes a human will (accidentally) unpin the issue, which requires another human then go back and re-pin it.

It'd be nice if we could have Renovate ensure that the Dependency Dashboard is currently showing as a pinned issue.

This would be something for repo-config.

This would be platform-specific.

[RahulGautamSingh]

Is it possible to do that via API or gh cli?

[jamietanna]

It looks like for GitHub it's via GraphQL (i.e.)

[rarkins]

What permissions are required to pin issues?

I think you'd want to make "enforcing" it optional. Eg "enabled", "disabled", "enforced". That way it can be turned on per org but teams can unpin it if they prefer

Can we determine "is this already pinned?" Using our existing API calls? We wouldn't want to use an extra API call per job just for this.