architecture option for runners that are not amd64 #10

Closed
opened 2024-03-04 09:17:37 +00:00 by leana8959 · 1 comment
Contributor

Hello,

Since my runner is running on arm64, I had to fork the project and change the architecture for it to work (the binary of tea).

I have two ideas to implement this:

  • parse the output of uname -m and decide which arch to use
  • expose an option architecture to users of this action for them to override based on the arch of their runner

If it's a change that might be useful for others too, I could create a PR.

Thanks =)

Hello, Since my runner is running on arm64, I had to fork the project and change the architecture for it to work (the binary of `tea`). I have two ideas to implement this: - parse the output of `uname -m` and decide which arch to use - expose an option `architecture` to users of this action for them to override based on the arch of their runner If it's a change that might be useful for others too, I could create a PR. Thanks =)
Owner

Absolutely! A very welcome addition. You will see there is a rather complete test suite to exercise this action. If you get it running with an ARM64 runner and produce AMD64 releases, that would be quite useful for other people.

Absolutely! A very welcome addition. You will see there is a rather complete test suite to exercise this action. If you get it running with an ARM64 runner and produce AMD64 releases, that would be quite useful for other people.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: actions/forgejo-release#10
No description provided.