gm3dmo/the-power

The Power is a bunch of test scripts that share a single centralized configuration file for use with GitHub API's. It's commonly used by folks with a need to teach, learn, debug against GItHub's API's in a rapid fashion.

The Power

Table of Contents

1. What is the Power?
2. Setup Instructions
3. Contributing to The Power
4. Known Issues/Problems/Solutions
5. Testcases
6. Setting up a GitHub App to use with The Power
7. GitHub API Learning Resources
8. Scaling to create larger environments

What is The Power?

The Power is a simple test framework for GitHub's API's. It's goal is to help you learn to interact with and understand GitHub API's by building test scenarios such as; a repository with a pull request, teams and users on a testing instance of GitHub Enterprise or GitHub.com a pre-existing Organization and Enterprise Account.

The Power can create the following on a blank appliance or organization in <=30 seconds:

• An Organization.
• Users
• A team of users.
• A private repository named testrepo with a branch called new_branch,
• Branch protection rules on branch main.
• CODEOWNERS file configured for the README.md and .gitattributes files.
• An Issue with the label bug.
• A pull request with a code owner requested for review. The pull request contains 2 commits against 2 files and activates the tree view.
• A manifest file for a package manager file with a vulnerability to trigger Dependabot.
• A webhook on testrepo that outputs to it's own smee.io url.
• A Release.
• GitHub Pages configured for testrepo.
• A Gist.
• Mermaid diagrams using create-commit-mermaid.sh to demonstrate the GitHub supported diagram types on the mermaid project.

There are many other features and test-cases you can use or adapt to build scenarios of your own.

The Power is a tool for learning

• Designed to be as simple as possible to understand. To keep things simple we exclusively uses only curl and jq to complete most tasks. Only a few of the more complex scenarios have other dependencies.

The Power is vast and deep

There are hundreds of pre-baked scripts to:

• Create commits, secrets, hooks, issue comments, environments.
• Bulk up your appliance by creating hundreds or thousands of users/orgs/repos/teams/pull requests.
• Set up a Tiny GitHub App in less than 1 minute.
• Demonstrate GitHub Actions.
• Demonstrate Code scanning.

The Power is highly configurable

The configuration file .gh-api.examples.conf is the green fuse that drives The Power. The configuration file format is a simple list of key value pairs:

### [Branches](https://docs.github.com/en/rest/commits/commits)
# https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/
proposing-changes-to-your-work-with-pull-requests/about-branches
branch_name="new_branch"
protected_branch_name="main"
required_approving_reviewers=1
required_status_check_name="ci-test/this-check-is-required"
enforce_admins="false"
base_branch=main

The Power's configuration can be shared with other tools

The use of kv pairs in .gh-api-examples.conf provides maximum flexibility and simplicity. It allows the configuration file to provide the basic descriptors for other more advanced tools like Apache JMeter or hurl

Hurl using the .gh-api-examples.conf file

hurl-repo-characteristics.sh shows hurl provisioned with values .gh-api-examples.conf:

hurl --test --variables-file .gh-api-examples.conf --json hurl-tests/repo-characteristics.hurl | jq -r

The hurl-tests/repo-characteristics file looks like:

GET {{ GITHUB_API_BASE_URL }}/repos/{{ org }}/{{ repo }}
Accept: application/vnd.github.v3+json
Authorization: token {{ GITHUB_TOKEN }}

HTTP/2 200

[Asserts]
status >= 200
status < 300
header "Content-Type" == "application/json; charset=utf-8"
header "x-github-request-id" isString
jsonpath "$.name" == "{{ repo }}"
jsonpath "$.full_name" == "{{ org}}/{{ repo }}"

Why The Power

There are lots of great tools like Postman, JMeter for interacting with API's and building testsuites and many of the latest API's come with their own interactive documentation built-in like the swagger petstore. The Power is a solution for times and places where those tools just aren't available.

the-power's Issues

gh extract token

you can extract the token using go-gh or from CLI invocation

 gh config get -h github.com oauth_token                                                                                                                                         

homebrew `base64` vs `/usr/bin/base64`

I found that the homebrew version of base64 does not seem to work the same way as the mac delivered /usr/bin/bas64 version:

➜  b1 git:(main) ✗ /opt/homebrew/bin/base64 --help
base64  --  Encode/decode file as base64.  Call:
            base64 [-e / -d] [options] [infile] [outfile]

Options:
           --copyright       Print copyright information
           -d, --decode      Decode base64 encoded file
           -e, --encode      Encode file into base64
           -n, --noerrcheck  Ignore errors when decoding
           -u, --help        Print this message
           --version         Print version number

by John Walker
http://www.fourmilab.ch/

➜  b1 git:(main) ✗ /usr/bin/base64 -h
Usage:	base64 [-hDd] [-b num] [-i in_file] [-o out_file]
  -h, --help     display this message
  -Dd, --decode   decodes input
  -b, --break    break encoded string into num character lines
  -i, --input    input file (default: "-" for stdin)
  -o, --output   output file (default: "-" for stdout)

Include a mermaid diagram in the default pull request

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Implement GH Actions reusable workflow reproduction along with env secret inheritance

It would cut down to zero repro times if Power can implement GH Actions reusable workflow reproduction along with env secret inheritance.

Under an org on GHEC:
-Two private repos
-Repo A - Private - (will contain the reusable workflow) -> Settings -> Accessible from repositories in the 'XYZ' organization
-Repo B - Private - (will contain the caller workflow). Create env and env secret in the caller repo for this to work.

cc: @gm3dmo

Define repository has_discussions etc in configuration file

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
Take the configuration values out of the script create-repo-testrepo.sh and allow them to be passed as configuration values.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

python poetry

create-commit.sh has a hardcoded sha fro tree_sha and the ${json_file} is missing on lines 15 and 21

Describe the bug
create-commit.sh has a hardcoded sha fro tree_sha and the ${json_file} variable is missing on lines 15 and 21

To Reproduce
Check lines 14, 15 and 21

Expected behavior
The tree sha shoudn't be hardcoded
On lines 15 and 21 you ${json} should be ${json_file}

Java maven manifest format

Add merge queue api examples

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like

Samples for:

https://github.blog/changelog/2023-04-19-pull-request-merge-queue-public-beta-api-support-and-recent-fixes/

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

When I'm adding a PR against the-power the pull request template is nonsensical

The repositories pull request template is nonsensical, probably because it's used somewhere in the-power:

# Code Review Template:
- [ ] Carfarfar barfarfarfr barfr bar barfaa? Yar => Carfa
Narf: 
- [ ] Saar br barfr bar barfaar barfarfr barfar baar br bar barfarf.? Yar => Carfa
- [ ] Dr bar barfar barfarfr baar barfarfarfaa? Nr => Carfa
Carfaar barfr barfaar (a.a. baar barfaar barfa) barfr bar baar baar br baar bar bar br barfar br barf.
- [ ] Ir bar barfar barfarfaar br b baar (.a) bar b barfar baar (.a) barfr br bar barfarfr barfarfar (arfarfaar br bar PMT barfarfr barfa), br barfr br barfar baar bar barfar barfarfarfaa? Yar => Carfa
Sarfarfr barfaar barfaa, barfarfaar br barfr barfarfr barfarfarf, barfarfr barfr br barfarf, barfr br bar barfarfar barfarfr (arf/aar barf, barf/arfr barf, barfaa...), baa...
- [ ] Aar bar barfarfar (arfaa) barfarfar barfaar barfar barfarfar barfarfarfr br bar barfarfarf? Yar => Carfa
- [ ] Aar barfr baar baar 700 barfarfar barfr br baar br bar barfaa? Nr => Carfa
- [ ] Ir barfr bar barfarfr baar baar baar 100 barfarfar barfr br barf? Nr => Carfa
- [ ] Aar bar barfaar barfarfarfr barfarfarf? Yar => Carfa
Parfar barfr br barfr barfarfr baar /*arfr …, //arfr … bar /* baar … baar b barfarfar br bar MISRA barfarfar baar bar br bar barfarfar br barfarfarf.
- [ ] Ir barfr bar barfarfr baar b barfarfaar barfarfaar barfar barfaar baar 15? Nr => Carfa
- [ ] Aar bar barfar barfarfr baar br barfarfar barfarfaar barfr (arfarfarf, barfarfaar barfr baar bar barfarfaa) br barfarfr barfarfr barfarfr br barfarfa? (Tr barfr barfarfaar barfarfarfaa) Yar => Carfa
- [ ] Aar bar barfarfaar br barfr br barfarfr barfar barfarfar barfarfar br barfr barfar barfarfaa? Yar => Carfa
Ir barfarfr br bar baar bar baar barfaa, bar Nar bar barfarf.
- [ ] Tarfr br bar barfar barfar br HW barfarfaa? Nr => Carfa
Aarfar br barfarfar br barfaar baar bar barfarfr barfarfa.
- [ ] Ir bar baar barfarfar br baar baar barfaa? Daar baar baar barfaar bar br barfr baar br barfarfar barfar barfarfaa?  (arfa-arf, ...) Yar => Carfa
E.a. barfa(SPI_DONE == FALSE) { ... } /* bar OK – barfarfr br bar barfarfarfaar barfr */
- [ ] Ir barfr bar barfaar barfarfr br bar barfar bar baar barfaar b barfr br br barf? Nr => Carfa
Darfarfaa: '0' bar '1' bar barfaar br barfarfaar baa-arfarfr barfarfar (a.a., baar barfarfa). '1' br baar barfaar br bar barfaar barfr br barfr "aar barf" br "aar barf" (a.a., baa-1 br b[a+1]).
- [ ] Far baar barfarfa, br bar baar barfr barf, barfaar barfarfr barfarfaar bar barfr barfarfaa, barfarfr br br barfarfarf? Yar => Carfa
Aarfar  bar barfaar barfarfaar barfar bar br br barfa.
- [ ] Ir bar “?:” barfarfar baar baar br bar barfaar barfaar barfaa, barfaar br barfar br barf? Yar => Carfa
- [ ] Aar bar barfarfr barfar bar baar barfaar bar barfr barfarfr barfar (EEPROM baar barfar br barfarfaar br barfarfa)? Yar => Carfa
- [ ] Aar bar TRUE barfr baar br barfarfarfa? Nr => Carfa
E.a. br (IaRarfarf() == TRUE) bar baar br barfaar bar barfr barfr baar 1. Uar br (IaRarfarf() != FALSE) barfarf.
- [ ] Ir barfr bar barfarfr (==) barfr br bar baar barfr barfarfaar (arfarfarfr (<, <=, >, >=) bar br baar barfarf? Nr => Carfa
Aar baar barfarfarfr barfarfaar baar bar barfarfarfaa. Earfarfr barfr br OK bar barfaar baar br baar baar barf.
- [ ] Ir bar barfr barfarfr baar Earfaar baar br bar barfar barf? Nr => Carfa
- [ ] Ir barfr bar "arfaa" barfar br barfr bar "." bar bar "->" barfarfaa? Nr => Carfa
- [ ] Ir barfr bar "arfaa" barfaar "++", "--", "&" , "~","!", (arfarfaaAarfarf) , "*" (FarfarfaRaa) barfarfar bar bar barfarf? Nr => Carfa
- [ ] Ir barfarfaar br barfarfa: bar bar barfarfaar br barfar barfr barfarfar bar barfarfar br bar barfarfarfaar baar barf? Yar => Carfa
- [ ] Dr bar barfarfarfr barfaar bar barfarfaar barfarfarfa? Nr => Carfa
- [ ] Aar bar barfaar baar barfarfr barfarfr baar <> bar barfaar barfaar baar ""? Yar => Carfa
- [ ] Ir bar ".a" baar barfarfr br barfarf? Nr => Carfa
- [ ] Ir barfr b barfarfr baar baar barfaar bar baar barfarfa? Yar => Carfa
- [ ] Aar barfr bar barfarfr barfarfarfr br bar baar barfarfarf? Nr => Carfa
(arfarfarfr baar b=a=a; bar bar OK)	
- [ ] Aar bar "++" bar "--" barfarfar baar br barfarfarfr barfarfr baar barfr barfarfaa? Nr => Carfa
- [ ] Aar bar "++" bar "--" baar br barfaa? Nr => Carfa
- [ ] Ir bar barfarfr barfar bar barfr barfarfar bar barfarfr br barfar barfar br barfarfa? Nr => Carfa
- [ ] Ir bar barfarfr barfar bar barfr barfarfar bar barfarfr br barfarfr barfaar barfaar br barfa? Nr => Carfa
- [ ] Ir C baar barfarfr barfarfr barfarfa, br br bar b barfr C barfarfa? (aar bar baar bar b baar br bar C barfarfa) Yar => Carfa
(Aarfarfr barfaar barfar b BSW/SWP barfr br OK)
- [ ] Ir barfr bar bar barfar barfar br b barfar baar baar barfr barfar br bar bar baar bar bar barfar bar barfaa? Nr => Carfa
Far barfaar barfarfar b baar br baar bar bar barfr barfr br barfar barfaa. Oaar bar barfr br barfarfr T_FLAG8, T_FLAG16 br barfaar bar baar barfarfa
- [ ] Aar barfarfar barfr baar br bar barfarfarfr bar barfarfaar br b barfarfr barfarfaa? Yar => Carfa
- [ ] Ir barfr bar barfaar barfarfaar barfaar br barfarfr barfr br bar barfaar bar barfr br br barfr barfarf? Nr => Carfa
Parfaar barfarfaar br barfaar baar bar barfr barfarfr barfarfa.
- [ ] Ir barfr bar barfarfaar br barfar baar barfarfar br barfarfarfr barfaar br barfar barfa/arfarfa? Nr => Carfa
E.a.: barfaa( &arfaa[1], &arfaa[4], 8 ); /* barfarfarfr bar barfar barfaar */
- [ ] Ir barfr bar barfar barfaar baar br barfr baar baar br bar barf, bar baar br barfr b barfarfar baar br baar br barfaar barf? Nr => Carfa
E.a. Tar baar barfarfr baar bar bar barfarfar barfarfa.
- [ ] Ir bar barfarfr br barfar (arfaa/arfr barfaa) br baar baar bar baar (a.a. barfarfar barfaar + barfarfaar barf), br br barfarfaa? Nr => Carfa
- [ ] Ir barfr b barfarfar br barfr b baar barfar b barfar br bar barfar barfarfa? Yar => Carfa
- [ ] Ir barfr b barfarfar br barfr baar barfarfarfar barfar bar barfarfaa? Yar => Carfa
- [ ] Ir baar br barfar barfarfr (arfaar br bar barfaa) baar br barfarfar barfarfr (arfarfarfr barfar br br ISR), br barfr b barfarfar br barfr baar barfarfarfar barfar bar barfarfaa? Yar => Carfa
- [ ] Ir baar barfa/arfarfaa-arfr barfr barfarfr barfarfaar (a.a. ENTER_PROTECTED_SECTION, SarfarfAaaIarfarfarf()) barfarfr br barfarfar bar barfarfr barfr (a.a. LEAVE_PROTECTED_SECTION, RarfaaAaaIarfarfarf()) br bar barfa? Yar => Carfa
- [ ] Dr C bar barfar barfr baar barfaar barfr barfar barfr barfr barfaar barfaar barfar baar br baar barfa? Yar => Carfa
- [ ] Ir barfr bar barfarfr barfaar b barfaar barfar barfarfaar bar barfaar br bar barfarfr bar bar ba/aar barf? Nr => Carfa
- [ ] Aar barfr baar baar barfarfr barfar br  barfaar barfaar barfarfar barfaar br b barfar br #arfarfa? Yar => Carfa
- [ ] Aar barfr barfarfar barfaar br barfarfarfaa? Yar => Carfa
- [ ] Aar barfarfaar baa/ar barfarfaar br bar barfr barfarfr baar barf/arfaar bar barfarfarfr barfarfaa? Yar => Carfa
- [ ] Aar baar barfar br b barfar barfarfar barfaar bar barfr (arfarfaar baar baar #arfarfa)? Yar => Carfa
- [ ] Oaar bar barfarfr barfr SWP: br bar barfar barfarfar baar barfarfarfaa? Yar => Carfa
Sar barfaar br baar baar bar barfarf.
- [ ] Aar bar barfaar barfarfarfar barfarfar br baar barfr baa? Yar => Carfa
Aar barfarfarfar barfar br barfarfar bar bar barfaar barfarfarfar br barfarfaa.
Tarfr barfar bar br baar baar bar barfarfarfr br b barf.
- [ ] Ir barfr bar baar barfaar barfarfar baa? Nr => Barfa
- [ ] Aar bar barfarfaar barfarfarfar br bar barfr br bar ISR? Yar => Carfa
Or barfaar barfarfar (ar b850 FX3) "arfarfaar barfarfarfarfaa" br baar barfarfarfaar br HW baar ISR br barfarfr baar barfarfaa.
Harfaar br barfr barfarfar (ar HC12, S12r baa) "arfarfaar barfarfarfarfaa" bar br br baar barfarfaar br barf.
- [ ] Aar barfr bar barfarfar br baar barfr barfr baar baar barfarf? Nr => Carfa
- [ ] Aar barfr bar barfarfar br bar baar barfr barfar br baar br bar barfarfaar barf? Nr => Carfa
Aarfarfar barfr br baar baar br barfar barfarfr barfarfr barfaa.
- [ ] Ir barfr bar barfr barfaar bar barfr barfarfr baar b barfar barfarfarfa, b barfarfa, b barfarfarfaar barfarfarf, b baar barfarfaa, barfaar barfr barfarfar br b ba-arfaa-arfr barfarfaa? Nr => Carfa
Far barfaar br barfar baar (arfarfr br barfr barfarf) br br barfaar C barfarfr barfarfr (a.a. #arfaar IF ba)
- [ ] Far baar barfar barfr br b barfarfar br barfr barfar barfarfaa? Yar => Carfa
Earfarfaa: MaaMaa.a
- [ ] Aar bar barfarfarfar barfarfaar barfarfarfaar barfaar baar bar barfarfr barf? Yar => Carfa
Par barfarfar br bar #arfa, #arfr bar #arfar barfr barfr br barfarfaar bar bar barfarfr br bar barfarfa.
- [ ] Ir barfr bar #arfa, #arfr bar #arfar barfr br bar barfar br bar baar baar br bar barfarfarfaar #ar br #arfar barfarfaa? Nr => Carfa
- [ ] Aar bar barfarfarfr barfar bar bar barfarfar barfarfaar bar baar barfarf? Yar => Carfa
- [ ] Ir bar barfa, br bar barfaar barfarfr baar bar barfarfar barfarfr barfarfr br bar baar br bar barf? Nr => Carfa
- [ ] Ir barfr bar barfarfr baar baar baar bar baar barfa? Nr => Carfa
- [ ] Ir barfr bar barfar barfarfar barfr  barfar barfar barfar bar barfar barfaar barfaar barfarfaar barf? Nr => Carfa
- [ ] Ir barfr bar barfar barfarfar baar baar baar barfr baar barfarf? Nr => Carfa
- [ ] Ir barfr bar barfarfarfr (arfaar br barfarfa)? Nr => Carfa
- [ ] Ir barfr bar barfarfr barfarfaar barfaar bar & barfarfr br barfarfarfaar barfarfar barf? Nr => Carfa
Earfar baar bar baar br barfarfr barfarfr (arfarfar barfr barfaar barfarfarfa) bar barfar barfarfa.

Ruby RubyGems

Provide an `${owner}` variable future use alongside/replace the `${org}` variable

Add app_client_secret capability to The Power

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like

.  ./.gh-api-examples.conf

# https://docs.github.com/en/rest/apps/oauth-applications?apiVersion=2022-11-28#delete-an-app-token
# DELETE /applications/{client_id}/token

curl \
      -X DELETE \
     --user "${client_id}:${app_client_secret}" \
     --header "X-GitHub-Api-Version: ${github_api_version}" \
     --url "${GITHUB_API_BASE_URL}/applications/${client_id}/token" --data '{ "access_token": "ghu_elXBc3XawKfVZfehqJbxauErc8WSZA1DyblE" }'

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

`.gh-api-examples.conf` doesn't work so well with zsh which likes to work with `./.gh-api-examples.conf` on line 1

Describe the bug
Doesn't work so well with zsh zsh likes to work with ./.gh-api-examples.conf on line 1

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
Works in zsh as well as bash.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

JavaScript Yarn

Suggestion: add a mermaid example

Here is one of the examples mermaid provided by the live editor:

graph TD
    A[Christmas] -->|Get money| B(Go shopping)
    B --> C{Let me think}
    C -->|One| D[Laptop]
    C -->|Two| E[iPhone]
    C -->|Three| F[fa:fa-car Car]

python pip

Have a change in the default pull request to a file in /docs to activate the tree view of a pull request

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

ghes-* commands are broken with port and admin password settings

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

configure.py: error: argument --pr-approver-name: expected one argument

Describe the bug
when running zdpower foo I get an error: "configure.py: error: argument --pr-approver-name: expected one argument"

To Reproduce
Steps to reproduce the behavior:

1. zdpower foo
2. get the following output:

%  zdpower foo
Cloning into 'foo'...
remote: Enumerating objects: 2513, done.
remote: Counting objects: 100% (686/686), done.
remote: Compressing objects: 100% (541/541), done.
remote: Total 2513 (delta 392), reused 271 (delta 140), pack-reused 1827
Receiving objects: 100% (2513/2513), 2.72 MiB | 1.33 MiB/s, done.
Resolving deltas: 100% (1407/1407), done.
./dotcom-configure.sh /Users/mokshadharma/.the-power-dotcom.conf repo-foo
usage: configure.py [-h] [-o ORG] [-b BASE_BRANCH] [-d CONFIGURE_GITHUB_APP] [-a APP_ID] [-i INSTALLATION_ID] [-e CLIENT_ID] [-u ADMIN_USER]
                    [--admin-password ADMIN_PASSWORD] [-w WEBHOOK_URL] [--number-of-users NUMBER_OF_USERS_TO_CREATE_ON_GHES]
                    [--runner-version RUNNER_VERSION] [--runner-os RUNNER_OS] [--runner-platform RUNNER_PLATFORM] [-c DOTCOM_CONFIG] [-r REPO_NAME]
                    [-n HOSTNAME] [-t TOKEN] [-l LOGLEVEL] [-p PRIMER] [--private-pem-file PRIVATE_PEM_FILE] [--number-of-orgs NUMBER_OF_ORGS]
                    [--number-of-repos NUMBER_OF_REPOS] [--number-of-teams NUMBER_OF_TEAMS] [--number-of-branches NUMBER_OF_BRANCHES]
                    [--team-members TEAM_MEMBERS] [--team-admin TEAM_ADMIN] [--default-committer DEFAULT_COMMITTER] [--allow-auto-merge ALLOW_AUTO_MERGE]
                    [--delete-branch-on-merge DELETE_BRANCH_ON_MERGE] [--enterprise-name ENTERPRISE_NAME] [--pr-approver-token PR_APPROVER_TOKEN]
                    [--pr-approver-name PR_APPROVER_NAME] [--preferred_client PREFERRED_CLIENT] [--custom-curl-flags CURL_CUSTOM_FLAGS]
                    [--preferred_browser PREFERRED_BROWSER] [--preferred_browser_mode PREFERRED_BROWSER_MODE] [--github-api-version GITHUB_API_VERSION]
configure.py: error: argument --pr-approver-name: expected one argument

Expected behavior
successful run without errors

Screenshots
N/A

Desktop (please complete the following information):

• OS: MacOS Ventura 13.2.1
• Browser: None
• Version: N/A

Additional context
none

Add a commit message to the merge pull request script

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

https://docs.github.com/en/free-pro-team@latest/rest/pulls/pulls?apiVersion=2022-11-28#merge-a-pull-request

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

broken link: create your token

on https://github.com/gm3dmo/the-power/blob/main/docs/setup.md the link to create your token is pointing at https://github.com/gm3dmo/the-power/blob/main/docs/1 which doesn't exist (I'm not sure where it's supposed to be pointing or I'd have PR'd a fix)

Add an issue form

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms

base64: invalid argument test-data/python/pip/requirements.txt_

Describe the bug
During a run of bash build-all.sh I got an error:

+ ./create-commit-python-pip.sh
base64: invalid argument test-data/python/pip/requirements.txt_
Usage:  base64 [-hDd] [-b num] [-i in_file] [-o out_file]
  -h, --help     display this message
  -Dd, --decode   decodes input
  -b, --break    break encoded string into num character lines
  -i, --input    input file (default: "-" for stdin)
  -o, --output   output file (default: "-" for stdout)

To Reproduce
Steps to reproduce the behavior:

1. Download and untar https://github.com/gm3dmo/the-power/archive/refs/tags/1.0.173.tar.gz
2. In #support-ops, type .gheboot 3.7
3. Log in to the appliance and manually create a PAT with all permissions
4. Run 'python3 configure.py' and answer the questions, paste in your token etc.
5. Run 'bash build-all.sh'
6. Get the base64 error pasted above

Expected behavior
No error.

Screenshots
None

Desktop (please complete the following information):

• OS: MacOS Ventura 13.1
• Browser: Chrome
• Version 108.0.5359.124

Smartphone (please complete the following information):
N/A

Additional context
N/A

Javascript NPM

Modify the `/docs/README.md` file to trigger team review request for a CODEOWNERS team

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Support creation of PHP Composer lock files

https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#supported-package-ecosystems

Use the word `Bearer` in the auth_header to replace the word token

Getting started with the Rest API

curl --request GET \
--url "https://api.github.com/octocat" \
--header "Authorization: Bearer YOUR-TOKEN"

This is defined in configure.py:

auth_header="Authorization: token ${token}"

Replace token with Bearer

Create scripts for codespaces API

https://docs.github.com/en/rest/codespaces

The gh cli is capable of doing these so it may not be worth duplicating.

Set the default branch protection rule to tick on `Do not allow bypassing the above settings`

Create a rust example cargo manifest

Have create-many-teams work from the same feed as users and orgs

Evaluate removing the tiny app's dependency on ruby and replace it with python3 if possible

Ruby and it's jwt gem are needed for the jwt generation. If this doesn't need a python module then we could replace ruby with python for the jwt. If it needs a pip install then don't.

Remove redundant site-b feature

The site b thing is redundant. I added it because I saw the kids watching Jurassic Park 2 and I thought it was cool that the old dude had the foresight to make a backup of the dinosaurs.

create-branch-protected.sh in `build-testcase` responds with "Reference already exists"

+ ./create-branch-protected.sh
4c29d16a9160b79e3edd7b928c6c99dc1aa7b0fd
{
  "message": "Reference already exists",
  "documentation_url": "https://docs.github.com/rest/reference/git#create-a-reference"
}

https://ghe.io/gm3dmo/the-power/blob/main/create-branch-protected.sh

Go modules

New issue

https://github.com/Sebastianoskiojoj/the-power/blob/main/create-commit-workflow-build-push-docker.json

Add scripts for organization repository rules

Is your feature request related to a problem? Please describe.

https://github.blog/changelog/2023-04-17-introducing-repository-rules-public-beta/#:~:text=Repository%20rules%20are%20GitHub's%20next,enforce%20them%20across%20your%20organization.

https://docs.github.com/en/rest/orgs/rules?apiVersion=2022-11-28

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

add issue templates

https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

something to seperate bugs, feature requets, improvements etc.

Add mermaid c4 diagram to examples

GitHub.com's mermaid rendering recently integrated mermaid C4 .

Capability to demo this diagram should be added to the power.

Add a render markdown example

Is your feature request related to a problem? Please describe.

https://docs.github.com/en/rest/markdown/markdown?apiVersion=2022-11-28#render-a-markdown-document

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Provide a flag for `delete_branch_on_merge` and set the default value to `true`

add reference org dependencies github action

https://github.com/andyfeller/gh-dependency-report

update the actions versions in the codeql zipslip demo

Provide a testcase for Tiny GitHub App to "sign" code

Missing a "C" on line 34 on docs/setup.md

the-power/docs/setup.md

Line 34 in fabe0ee

### onfigure.py can run without interaction from the command line:

Support creation of Nuget .NET formats

Add support for version header to the power

With the new API structure supporting X-GitHub-API-Version header, some of the API calls are failing. Add support for a standard version latest and a way to override it.

Suggestion: move the scripts to a subfolder so the readme is visible

Just a lot of noise in the root of the folder, so keep the config and mandatory files in the root and moving everything else to subfolders.

Pull request review comments don't appear

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.