Update accessing-contextual-information-about-workflow-runs.md

[lachieh]

Why:

I needed to pass the repository URL to a 3rd party action and used the github.repositoryUrl property. It took some digging to find out why the operation was timing out, but I eventually stumbled across a blog post which says to basically just stop using the git:// protocol.

What's being changed (if available, include any code snippets, screenshots, or gifs):

Adding a note below the table to mention this restriction.

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require a SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing.

[github-actions]

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.

---

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source	Preview	Production	What Changed
actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10

---

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server

[nguyenalex836]

@lachieh Thanks so much for opening a PR! I'll get this triaged for review ✨

[felicitymay]

Many thanks for reporting back on your discoveries about the git:// protocol and proposing a useful alternative for users. It's much appreciated 💖

I'm suggesting that we move the information directly into the table. However, before we merge any updates, we should follow up internally because it feels as if the output of github.repositoryUrl should have been updated when we turned off the git:// protocol.

[github-actions]

Thanks for opening a pull request! We've triaged this issue for technical review by a subject matter expert 👀

[lachieh]

Thanks, @felicitymay!

it feels as if the output of github.repositoryUrl should have been updated when we turned off the git:// protocol.

I'm going to assume that the output was not modified because it can still be used for string comparison despite it not working for git operations. It seems like it is still used a fair bit.

In most cases, the actions/checkout action is enough as it configures the runner with the correct remote URL anyway. I needed the https URL for a different 3rd-party action and had to dig a bit to work out why the github.repositoryUrl wasn't working specifically for git operations. I just didn't want others to waste time following the same path.