Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Add config to provide git push options#3159

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Draft
MatthewJohn wants to merge2 commits intosemantic-release:master
base:master
Choose a base branch
Loading
fromMatthewJohn:master

Conversation

@MatthewJohn
Copy link

I've created this change for myself (currently in testing) and created the PR to see if you believe it would be useful.

The rational behind this:

  • I use Gitlab primarily but replicate to Github.
  • Some projects use both Gitlab CI/CD and Github actions (mainly for testing/tagging etc. in Gitlab and then producing artifacts in Github).

When I merge into Gitlab, semantic release runs on main and performs the release. The release commit, by default, uses[skip ci], which is appropriate for Gitlab. Unfortunately, when the release commit is replicated to Github, italso respects this and skips Github actions.

This change means that I change the commit message, removing [skip ci] and use a git push optionci.skip (seehttps://docs.gitlab.com/ee/user/project/push_options.html), which will only skip the CI/CD pipeline in Gitlab.

I'm creating this PR to get feedback if it's a feature that you believe would be useful and, if so, I can tidy it up after testing, add tests etc. ready for proper review :)

Many thanks
Matt

maximgubar reacted with thumbs up emoji
@MatthewJohnMatthewJohn marked this pull request as draftJanuary 25, 2024 05:59
@MatthewJohnMatthewJohn changed the titleDraft: Add config to provide git push optionsAdd config to provide git push optionsJan 25, 2024
@maximgubar
Copy link

@MatthewJohn since this PR is still in draft I assume you have some temporary solution atm?
would be really interesting to see it, cause for me this 2 pipelines on each release is a bit annoying :)

@MatthewJohn
Copy link
Author

@MatthewJohn since this PR is still in draft I assume you have some temporary solution atm? would be really interesting to see it, cause for me this 2 pipelines on each release is a bit annoying :)

Hey@maximgubar,

I'm afraid I really can't remember - I don't think it was working exactly as I wanted it to. I'll take a look to see if I can remember which project I was trying to use this for and if I did have a workaround. Prior to making this change, the main thing I did was to adjust the commit message format to no longer include '[skip ci]' (https://github.com/DockStudios/jmon/blob/main/.releaserc#L20) and then added rules in the Gitlab workflow to ignore commit messages that were release-like (https://github.com/DockStudios/jmon/blob/main/.gitlab-ci.yml#L57).

I'll take a look to see if I can find evidence of a project using the changes in this PR to determine if they worked :D

Matt

maximgubar reacted with thumbs up emoji

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@MatthewJohn@maximgubar

[8]ページ先頭

©2009-2025 Movatter.jp