Repository navigation
Generate .gitignore files - #22
Merged
Merged
Conversation
added 2 commits
October 8, 2026 09:07
…odified and ignore all automatically-generated and overwritten code and configuration.
…omizable .gitignore files.
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
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.
Add .gitignore files to all generated projects.
The ignore rules depend on the project type:
.gitignorethat ignores only build files. Everything else should remain customizable and committable by users, since the generator is the primary place for manual changes. The template will be replaced with a concrete implementation that translates code from the source repository into project models according to the architecture description.src/directory and the Styles service inMETA-INF/services, so manual styling changes can be committed. See also a follow-up PR.