| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Hey @Dinara255 @TheGiraffe3, could you please merge this PR? |
Sorry, something went wrong.
Hi @PaulRBerg, thanks for your comment! If I'm not mistaken, neither @Dinara255 nor @TheGiraffe3 are maintainers of this repo (do correct me if I'm wrong). Maybe we should ping @salmanmkc or @robherley, who have recent contributions to the project. Btw, a more thorough explanation, with code snippets, can be found on the original issue: #1513 |
Sorry, something went wrong.
|
See also the fate of my related PR on this issue: |
Sorry, something went wrong.
There was a problem hiding this comment.
❤️
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Closes: #1513
Description
Update documentation, so that it reflects the actual behavior of cache-hit.
Motivation and Context
The documentation describes a behavior that does not reflect the actual implementation. This caused quite a headache when trying to debug this action.
How Has This Been Tested?
I updated my .yml so that they follow the logic in this PR and they worked correctly.
Types of changes
Checklist: