Creating workflow to open docs issue with need-docs label

[runleonarun]

Adding a workflow with automation that opens an issue in the dbt-labs/docs-internal repo when the needs-docs label is used on a pull request. The docs team will get notified when this is opened and work to document your change.

Slack message with more info
Notion doc with details and problem this is solving.

[cla-bot]

Thanks for your pull request, and welcome to our community! We require contributors to sign our Contributor License Agreement and we don't seem to have your signature on file. Check out this article for more information on why we have a CLA.

In order for us to review and merge your code, please submit the Individual Contributor License Agreement form attached above above. If you have questions about the CLA, or if you believe you've received this message in error, please reach out through a comment on this PR.

Test

Initiated test by adding the needs-docs label to this PR. You can see if an issue was open in docs-internal when this PR is merged.

CLA has been signed by users: @runleonarun

[runleonarun]

Initiated test by adding the needs-docs label to this PR. You can see if an issue was open in docs-internal when this PR is merged

[cla-bot]

Thanks for your pull request, and welcome to our community! We require contributors to sign our Contributor License Agreement and we don't seem to have your signature on file. Check out this article for more information on why we have a CLA.

In order for us to review and merge your code, please submit the Individual Contributor License Agreement form attached above above. If you have questions about the CLA, or if you believe you've received this message in error, please reach out through a comment on this PR.

CLA has not been signed by users: @runleonarun

[cla-bot]

Thanks for your pull request, and welcome to our community! We require contributors to sign our Contributor License Agreement and we don't seem to have your signature on file. Check out this article for more information on why we have a CLA.

In order for us to review and merge your code, please submit the Individual Contributor License Agreement form attached above above. If you have questions about the CLA, or if you believe you've received this message in error, please reach out through a comment on this PR.

CLA has not been signed by users: @runleonarun

[wolfram-s]

This is great!

Since I don't run GitHub actions, others (@akbog , @venkaa28 , @emmyoop ) maybe want to win in, but it is good enough for me.

[emmyoop]

Let me know if you need some help with the permissions. The trigger change is non-blocking.

[emmyoop]

I don't think this repo has access to this secret. It's not used in our public repos. Does FISHTOWN_BOT_PAT not have access to dbt-labs/docs-internal?

[runleonarun]

@emmyoop I don't see access in the Settings > Secrets & Variables > Actions for the docs public or internal repos.

I wonder if we should open the issue in the docs public repo similar to the Core workflow and just copy how we do it over there (secrets: inherit)? Or would this repo still require access to that secret?