-
-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
ignite: update go build and add completion support #199950
Open
chenrui333
wants to merge
1
commit into
master
Choose a base branch
from
ignite-build
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
+2
−0
Conversation
This file contains 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
github-actions
bot
added
go
Go use is a significant feature of the PR or issue
nodejs
Node or npm use is a significant feature of the PR or issue
labels
Dec 4, 2024
chenrui333
force-pushed
the
ignite-build
branch
from
December 4, 2024 00:15
c164bdb
to
81c18ba
Compare
chenrui333
changed the title
ignite: update go build and completion support
ignite: update go build and add completion support
Dec 4, 2024
chenrui333
force-pushed
the
ignite-build
branch
from
December 8, 2024 16:43
81c18ba
to
46dfcba
Compare
Signed-off-by: Rui Chen <[email protected]>
chenrui333
force-pushed
the
ignite-build
branch
from
December 9, 2024 20:27
46dfcba
to
2bdb3ea
Compare
SMillerDev
approved these changes
Dec 10, 2024
Build for macos stuck at some point,
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
go
Go use is a significant feature of the PR or issue
long build
Set a long timeout for formula testing
nodejs
Node or npm use is a significant feature of the PR or issue
shell-completion
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.
HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
, where<formula>
is the name of the formula you're submitting?brew test <formula>
, where<formula>
is the name of the formula you're submitting?brew audit --strict <formula>
(after doingHOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
)? If this is a new formula, does it passbrew audit --new <formula>
?