Replies: 1 comment
-
Octoherd creates a log file in NDJSON format by default. Everytime you use A super simple script would look like this /**
* The "Hello, World!" of all Octoherd Scripts!
*
* @param {import('@octoherd/cli').Octokit} octokit
* @param {import('@octoherd/cli').Repository} repository
*/
export async function script(octokit, repository) {
octokit.log.info(repository)
} Then you could use Another approach could be to load the repository settings from one repository and then compare them to all others, similar to what https://github.com/octoherd/script-sync-branch-protections Yet another approach could be to introduce script-specific options for the options you are interested in. I'm thinking about adding a reports feature to octoherd scripts, but I want to implement the Deno and Web runners first. Octoherd script should work across Node/Deno/Browser, so creating a CSV file directly from the script wouldn't be the Octoherd way, but of course you can do that anyway I've created an |
Beta Was this translation helpful? Give feedback.
-
Thanks for introducing octoherd at https://www.youtube.com/watch?v=qXHiXSSD3Kc. I think I remember you asked for octoherd script ideas, so here is one:
My usecase: I want to make sure all repos in my organisation have the correct configuration. I could click through all settings screens on all repos – which I do – but maybe this is a octoherd usecase.
Idea: Look at all given repos (orga, user, list). Create a line in a csv per repos. Columns could be common repos settings like "issues on/off", "projects on/off", "gh pages on/off", "gh pages url", etc. maybe also access information.
Beta Was this translation helpful? Give feedback.
All reactions