Be clearer on the expectations of running the automation scripts

[pauby]

Checklist

• I have verified that this is the correct repository, and the package is maintained by the chocolatey-community user.
• I have verified that this is happening in the latest available version of the package.

NOTE: I was asked to raise this issue here.

Current Behaviour

Recently working to try to pull this PR in for git.install, I ran the command, from the project root:

./update-all -name git.install

This gave me an error as it tried to update a gist without credentials. No package was built.

I then went into the /automatic/git.install directory and ran the command:

./update.ps1

This error was thrown:

Get-GitHubRelease : The term 'Get-GitHubRelease' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At Z:\git\chocolatey\fork\chocolatey-coreteampackages\automatic\git.install\update.ps1:7 char:20
+   $releaseAssets = Get-GitHubRelease -Owner 'git-for-windows' -Name ' ...
+                    ~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Get-GitHubRelease:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Expected Behaviour

When I try to update a package by manually running the scripts, it does not produce an error and creates a package.

Steps To Reproduce

See the Current Behaviour above.

Environment

- Operating System: Windows 11
- PowerShell Version: 5.1
- Shell: Windows Terminal

Anything else?

The issue was fixed in this commit.

If we expect people to be able to run the scripts as I did above, then we need to ensure they work and have everything they need to run inside them (for example, importing needed modules).

If we do not expect people to be able to runt he scripts, then we need to document:

1. That the scripts are not designed to be run manually.
2. What the process is for testing PR's.

[github-actions]

Thanks for raising this issue!

The packages within this repository are maintained by a small team of volunteer Community Maintainers, in their own time. Their time, like yours is important. Please help them by not wasting it.

This is a community repository where the expectation is that everybody will get involved by raising pull requests to fix problems they find. This will also allow that problem to be fixed more quickly as you don't have to wait for a member of the Community Maintainer Team to pick it up.

If you are unable to fix the issue yourself, the Community Maintainers Team will look at it when time allows. There are no service level agreements, nor should there be any expectation on when people can resolve issues in their own time.

A few dos and don'ts:

• Do provide as much information as you can in any issue that you raise.
• Don't complain that an issue has not yet been picked up or resolved. You are expected to help out in this community maintained repository. If you are unable to do so, don't complain when others don't adhere to your timelines. There is no SLA nor should you have any expectation of one.
• Do read the CONTRIBUTING and COMMITTERS documentation before raising a pull request as it contains valuable information on what automation is used in this repository.
• Do read the Code of Conduct.
• Don't post your frustration in comments. The Community Maintainers Team are not a punching bag for your frustration. You will only end up banned from the repository.

Thank you.
(Automatically posted message)