-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing protocol scheme #60
Comments
Hi there @DanielBadura, I'm sorry this causes you troubles. I believe the issue is that your |
The previous |
I think you misunderstood me. I already re-checked the |
Got it. I'm checking what's wrong there, my assumption is I did a mistake parsing the environment variables the right way. |
The environment variable parsing is fixed in v2.1.0 (https://github.com/cbrgm/mastodon-github-action/pull/61/files). The issue is not solved yet sadly. When I run podman run -e MASTODON_ACCESS_TOKEN="..." -e MASTODON_URL="https://mastodon.social" -e MASTODON_MESSAGE="Test Message" --rm -it ghcr.io/cbrgm/mastodon-github-action:v2 locally everything works as expected and I'm able to publish a message to Mastodon. But when I run the latest version in a workflow for some reason the secret values passed as environment variables to the container are somehow removed by GitHub (for security reasons?) (see: https://github.com/cbrgm/mastodon-github-action/actions/runs/9015989932/job/24771686465) . That's pretty weird, there must be something happening when GitHub passes the environment variables defined in a workflow file to the container during the workflow run. The environment variables are basically there but the value is empty e.g. In case this is blocking you, please just pass the URL and the Access Token as arguments to the action, this works fine @DanielBadura . - name: Send toot to Mastodon
id: mastodon
uses: cbrgm/mastodon-github-action@v2
with:
access-token: ${{ secrets.MASTODON_ACCESS_TOKEN }} # access token
url: ${{ secrets.MASTODON_URL }} # https://example.social
message: "Hello from GitHub Actions!" |
This issue is idle because it has been open for 90 days with no activity. |
I think this can be closed :) |
It still doesn't work for me. |
You mean with the env variables, right? I changed it from that to passing the variables directly. This is working for me and i saw the docs for v2 are using this variant instead, thats why I thought the issue can be closed. |
Passing env variables hasn't been completely removed as #61 suggests. There hasn't been anything about removing support for env variables in 2.0.0 release notes: https://github.com/cbrgm/mastodon-github-action/releases/tag/v2.0.0 Since it's still supported but broken, I think this issue should be reopened. I have about 14 repositories at https://github.com/phpstan/ tooting releases to Mastodon and I want to avoid updating them to action inputs instead of env variables. |
Hello 👋
we are currently getting an error:
Error posting status: API call error: Post "/api/v1/statuses": unsupported protocol scheme ""
This error just started to happen about 2 Weeks ago.
Last working job: https://github.com/patchlevel/event-sourcing/actions/runs/8687870377/job/23822282907
First failed job: https://github.com/patchlevel/event-sourcing/actions/runs/8734750142/job/23966065700
Between these 2 jobs the version was upgraded from v1 to v2. But i could find any BC-Break notices.
Worfklow file:
I already re-checked the
MASTODON_URL
and this ishttps://phpc.social
. And i also saw this issue here #55 which suggest adding inheriting secret which seems not to be needed for our case, right?I also saw another tool having the same problem: phpstan/phpstan-webmozart-assert#180
The text was updated successfully, but these errors were encountered: