Warn that renaming branches breaks actions

[jsoref]

Why:

If you rename a branch in a repository that hosts actions, workflows relying on those actions by branch name will break.

Closes [issue link]

What's being changed:

Add text to explain this.

Check off the following:

• I have reviewed my changes in staging. (look for the deploy-to-heroku link in your pull request, then click View deployment)
• For content changes, I have reviewed the localization checklist
• For content changes, I have reviewed the Content style guide for GitHub Docs.

[janiceilene]

👋 @jsoref Thanks for opening a PR! Can you add more information to the Why and What's being changed sections of the pull request template in the OP to help ensure this is triaged properly? Let me know when that's done and I'll get this triaged for review ⚡

[jsoref]

@janiceilene ⚡

[lecoursen]

Thanks @jsoref! I added a suggestion to move the new sentence slightly and use a product name variable, but I'll apply that suggestion and merge now!

[jsoref]

@lecoursen: can you please make this stop? (i.e. please send feedback to someone who will listen that they are dissuasive wrt external contributions)

It's really confusing and really unhelpful. Speaking as someone who is trying to make contributions to your project. (And many others.) I am now getting regularly haunted by these notifications.

I'm actually quite technical. But whether I wear a non-technical doc writing hat, or a technical code fixing hat, these notifications do not do me any good.

• They aren't actionable
• They are all sorts of red, which in normal terms means I should drop what I'm doing and do something to fix them. But I can't.
• They use a ⚠️ icon which should be 🟡 and paint it 🔴 (specifically 🔺). It's true that drivers may face a red yield icon, but not everyone drives (more importantly, that sign is 🔻), and why in the world would you use that iconography in this context?

[jsoref]

Fwiw, it looks like the most actionable action I can take here would be to click the shiny [ Disable auto-merge ] button. Which I'd be tempted to do if it would make the notifications go away.

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡

[janiceilene]

Oh my gosh @jsoref I'm so sorry about all of those notifications! The new "enable workflows" process was fighting with automerge on this one. Hopefully everything we'll get it all smoothed out soon, but in the meantime, I'll get this feedback to the right internal team.

Thank so much for your contribution! We really appreciate you sticking with us through this 💖