feat: source control .blink/config.json file #70
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
Update .gitignore templates to allow .blink/config.json to be committed while still ignoring other files in the .blink/ directory. This enables teams to share agent configuration across the repository while keeping build artifacts and temporary files out of source control. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Updates the
.gitignoretemplates used byblink initto allow.blink/config.jsonto be source controlled while still ignoring other files in the.blink/directory.Changes
.gitignorein bothscratchandslack-bottemplates.blinkto ignoring.blink/*with exception!.blink/config.jsoninit-templates/index.tswith updated templatesMotivation
When deploying an agent via GitHub Action, it requires an organization ID during
blink deploy. This information already exists in config.json and the file states that it's safe to be source controlled.