This repository has been archived by the owner on Aug 2, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 132
Incorrect DESTINATION_REPOSITORY value with release v2.12 #126
Comments
Thanks for the report! For now please use v2.11. We'll fix this soon! @m4heshd any way you can revise the repo matching to support all valid characters including ._- symbols, etc? |
@wei I'll take a look at it just in a few hours. I was waiting for something to go south after the release. 😆 |
m4heshd
added a commit
to m4heshd/pull-request
that referenced
this issue
Jan 21, 2023
m4heshd
added a commit
to m4heshd/pull-request
that referenced
this issue
Jan 21, 2023
@dcrossleyau Can you do a test using: - name: pull-request
id: open-pr
uses: m4heshd/pull-request@special-char-fix |
Hooray, yes that is verified. @m4heshd -- Thanks for your prompt attention. See successful run. |
wei
pushed a commit
that referenced
this issue
Jan 21, 2023
This is now released as |
Thanks to the responsiveness of all. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This pull-request action has been working beautifully for us for a long time. Thanks so much.
However today it broke with the v2.12 release.
Our repo is public:
https://github.com/folio-org/folio-org.github.io/actions/workflows/pr-config-apidocs.yml
For today's failed runs, see the "Gather Inputs" section where it has the incorrect value:
DESTINATION_REPOSITORY=folio-org/folio-org
i.e. the organization name instead of the repository name.
See the previous successful run which has the correct value:
DESTINATION_REPOSITORY=folio-org/folio-org.github.io
The text was updated successfully, but these errors were encountered: