Open
Conversation
Owner
|
Why did you close this PR? |
Author
|
I sent the PR with the wrong branch. |
beansofhell
approved these changes
Feb 19, 2024
* Update build-publish-docker.yml * Update build-publish-docker.yml
because previous one errors on a 404 fixing according to https://github.com/orgs/community/discussions/26274
Author
|
tested and still works. feel free to squash and merge at some point |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#9 didn't consider arm64 builds uses
Dockerfile.arm64.This PR will stop producing
ghcr.io/privacydevel/nitter:masterbut useghcr.io/privacydevel/nitter:latestand:latest-arm64like upstream.Note that with QEMU building with nim will take a long time, ~40 minutes. While upstream actions are using paid arm workers so it's way faster.