fix bug #107 #108
Open
fix bug #107 #108
Conversation
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
Member
|
Thanks for the PR @BorzdeG, but it looks like maybe an editor hook caused more lines to be updated than is needed for the change. Also, there's currently a conflict in |
…ty#114) * Update installation url to match repo url I also updated the command from `asdf plugin-add` to `asdf plugin add` to match the official documentation. Reference: https://asdf-vm.com/manage/plugins.html * Update plugin repository and CI status to asd-community for Go
* Add Makefile for Hygiene Signed-off-by: Sora Morimoto <[email protected]> * make format Signed-off-by: Sora Morimoto <[email protected]> --------- Signed-off-by: Sora Morimoto <[email protected]> Co-authored-by: Kenny Parnell <[email protected]>
Add loong64 support.
Co-authored-by: Kenny Parnell <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 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.
fix bug #107