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
When mocking a 404 for context.config('filename'), we need to do something like:
constrequests=nock('https://api.github.com').get('/repos/<owner>/<repo>/contents/.github/release-please.yml').reply(404).get(// why is this necessary?'/repos/<owner>/.github/contents/.github/release-please.yml').reply(404);
The text was updated successfully, but these errors were encountered:
bcoe
added
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
priority: p2
Moderately-important priority. Fix may not be included in next release.
needs work
This is a pull request that needs a little love.
and removed
triage me
I really want to be triaged.
labels
Sep 16, 2019
👋 I ultimately figured out why this is, it's actually probot behaving as expected.
It checks a .github folder in your existing repository, and if not found, checks for a .github repository in your organization (which can be used to store central config for a bot).
JustinBeckwith
added
type: cleanup
An internal cleanup or hygiene concern.
and removed
🚨
This issue needs some love.
needs work
This is a pull request that needs a little love.
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
labels
Mar 11, 2020
I'm actually going to go ahead and close this, as I think that it's behaving as expected (it just took us a while to notice that probot checks two repos for config).
When mocking a 404 for
context.config('filename')
, we need to do something like:The text was updated successfully, but these errors were encountered: