You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7a37e07
Browse filesBrowse the repository at this point in the historyBrowse files
init and setup explain how to create the App, and stop naming ours (#125)
Both told the adopter to create the simplycubed-code GitHub App. App names
are globally unique and we hold that one, so every adopter after us got
'Name has already been taken'. The step was only performable by the account
that already owns the App.
Neither said the thing that makes the rest make sense: the App has to be
theirs, because the private key is what mints tokens against their
repository and a shared key would let its holder act on every other
installation. Without that, 'create a GitHub App' reads as busywork we
could have done for them, and the natural response is to look for ours.
init now carries the creation URL, resolved to the org form when the
repository belongs to one, the three permissions with their access levels,
webhook off and why, install visibility and why it is the step most often
missed, and where the Client ID and the download-once private key come
from. A test asserts each element, so the gate holds prose it otherwise
could not judge.
docs/setup.md says the same things in the same order, and the references
to simplycubed-code[bot] as the adopter's identity now read
<your-app-name>[bot].
The decision record in docs/decisions is left alone: it documents a past
decision rather than instructing anyone.
Closes#110Closes#113
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -116,7 +116,7 @@ What that means for customers:
116
116
117
117
Setup files are generated locally by `simplycubed init` and then merged by a human, because the runtime holds no `workflows` permission and cannot add or update workflow files on its own.
118
118
119
-
The GitHub App identity is `simplycubed-code[bot]`. That bot is the single audit signal for everything the agent does.
119
+
The GitHub App identity is your own App's `[bot]` account. That bot is the single audit signal for everything the agent does.
120
120
121
121
## Getting started
122
122
@@ -143,7 +143,7 @@ Then follow the [setup guide in `docs/setup.md`](docs/setup.md) to add the repos
143
143
144
144
To run the loop inside your own GitHub Actions:
145
145
146
-
1. Create and install the GitHub App, `simplycubed-code`.
146
+
1. Create and install **your own**GitHub App. App names are globally unique, so it cannot be named after ours, and its private key is what mints the tokens that act on your repository.
147
147
Repository permissions: `Contents`, `Pull requests`, and `Issues` only.
148
148
Do not grant `Workflows`, `Administration`, `Environments`, or `Secrets`.
149
149
That means the App cannot push changes under `.github/workflows/`: if a run needs to edit a workflow file, make that commit as a human or run the CLI locally under your own `gh` auth instead of the App token.
0 commit comments