Skip to content

Conversation

genya0407
Copy link

Maybe related to #11.

I added the reporter-github-log_octokit option, which enables us to inspect octokit's request and response.
With this option, I believe we can debug our CI more easily.

Usage

See the explanation I added to README

Example

You can see the log example at https://github.com/genya0407/test-saddler-log-octokit/actions/runs/3213375525/jobs/5252994407

@sanemat
Copy link
Member

sanemat commented Apr 2, 2023

Great!

builder.use Octokit::Response::RaiseError
builder.use Octokit::Response::FeedParser
builder.response :logger, nil, { headers: true, bodies: { request: true, response: true } } do |logger|
logger.filter(/(Authorization: "(token|Bearer) )(\w+)/, '\1[REMOVED]')
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One of my concerns is leaking credentials to public ci log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants