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
console.log(`The github token was used to call ${result.method}${result.host}${result.path} but the permission is unknown. Please report this to the action author.`);
It generates markdown with a workflow snippet like:
* GitHub GraphQL API usage is not monitored. It would requires parsing and understanding the GraphQL queries. Pull-requests are welcome.
-It would requires parsing+It would require parsing
Expected results
Don't generate invalid workflow content
Do use # ... in the generated workflow content
Do surface the api call(s) -- if you're afraid of surfacing things, provide the client User-Agent, it should be possible to at least identify the objects being queried
The text was updated successfully, but these errors were encountered:
*`debug` - if set to `true`, the Monitor action will print additional debug information to the console. The default value is `false`. (Alternatively, debug logging can be enabled by restarting the runner with the debug checkbox marked or passing `debug` input parameter to the action.)
The current code is unhelpful for various reasons:
actions-permissions/monitor/index.js
Lines 76 to 77 in 3dcbd6b
It generates markdown with a workflow snippet like:
Minimal required permissions:
But if someone were to add this permission, it'd result in the workflow failing:
It doesn't use at least
::warning
or similar to call out the item https://github.com/jsoref/check-spelling/actions/runs/7331431111/job/19964051747#step:12:2The grammar in the readme is off:
actions-permissions/monitor/README.md
Line 62 in 8ecfc0d
Expected results
# ...
in the generated workflow contentUser-Agent
, it should be possible to at least identify the objects being queriedThe text was updated successfully, but these errors were encountered: