Make merge gatekeeper more resilient #67
Conversation
* ground works * cleanup * comments
README.md
Outdated
| @@ -16,7 +16,7 @@ At UPSIDER, we have a few internal repositories set up with a monorepo structure | |||
|
|
|||
| We are looking to add a few more features, such as extra signoff from non-coder, label based check, etc. | |||
|
|
|||
| <sup><sub>NOTE: | |||
There was a problem hiding this comment.
If you take out the blank spaces here, it would change the line break layout slightly. While it seems to read just fine with this change, I'd like to check if this was an intentional update?
There was a problem hiding this comment.
This is something very peculiar to our setup, but we are using Importer https://github.com/upsidr/importer for our documentation. This means we are only pulling in pieces of documentation from docs directory.
You can see some markdown comments such as
<!-- == imptr: inputs / begin from: ./docs/action-usage.md#[inputs] == -->It means it's checking the file ./docs/action-usage.md and a marker inputs, and when you run importer update README.md, it would replace the documentation with that given content. This is our own way of ensuring documentation does not get drifted between places, and that's the reason why the CI is failing. If you could make sure to update the ./docs directory content as well as README.md, that would be appreciated! 🥰
|
Btw, I'm so sorry for the extremely delayed review 🙇 |
* ground works * cleanup * comments * use importer to update docs * tests * rerender
|
Hi @rytswd, thanks for your comments and sorry for my delayed response too! |
Addressing Issue: #64 by adding a round tripper to perform retries.