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.
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
feat(sdk-schematics): initialize git repository #1361
base: main
Are you sure you want to change the base?
feat(sdk-schematics): initialize git repository #1361
Changes from all commits
5890cf2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should also add the
commit
optionYou can find an example in this file
packages/@o3r/workspace/schematics/ng-add/schema.json
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @matthieu-crouzet for your comment! I have added the
commit
option in the shell generator schematics. However, it is currently not used anywhere.I have some questions:
commit
option of the shell generator schematics betrue
by default?npm create @ama-sdk
command create a commit?npm create @ama-sdk
command use thecommit
option of the schematics to create a commit?yarn set version
nor the output of sdk generation... so for those extra changes, we could either create another commit or amend the previous one?I personally prefer not creating a commit in
npm create
(as it is done in the current state of this PR), but if it is decided to create one, then I think it would be better to create it directly with the right files (calling the shell generator schematics with thecommit
option set tofalse
and creating the commit at the end), rather than amending a commit. Note that if a repository already exists in a parent folder, theRepositoryInitializerTask
does nothing, so we should be especially careful not to amend a previous commit in this case.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed it should not be part of the
shell
schematic but more of thecreate
script at the end with all the files.It's the behavior that we have by default when run
npm create @o3r
if I'm not mistaken.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
npm create @o3r
creates a commit, but does not include all changes in it.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In your opinion should we create an issue to handle it later
I think it could be great if the repo is "clean" when you finish the creation