-
Notifications
You must be signed in to change notification settings - Fork 79
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
Documentation improvements. #258
Labels
Comments
This seems really sane to me and should be approved |
JonasSchubert
added a commit
to JonasSchubert/gitlab
that referenced
this issue
Apr 16, 2022
Hi. I created a small PR #366 to start working on this. Feel free to jump on and work on this. I just added the missing configuration for Regarding your remarks:
These are just my thoughts. Feel free to add and change the mentioned PR to optimize the documentation 😉 |
fgreinacher
added a commit
that referenced
this issue
Apr 26, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think it's a better to make these example uniform, it's really confusing.
semantic-release/gitlab
(this project)dist
hand has many "assets".npm pack
just needs to be told to thedist/
directory that contains thepackage.json
, for examplenpm pack dist/my-workspace/my-lib
. How do we package an angular project with Semantic-Release gitlab like above?gitlabUrl
in there. It's not clear why I would ever want that. That can be supported by thepackage.json
. Why would I want it here. For simplicity I would remove it.GitLab wiki,
The following is from the GitLab wiki,
branches
That seems to be required. If it is this project should probably also contain it.The text was updated successfully, but these errors were encountered: