Skip to content
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

Updated the entrypoint #39

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

chougule007
Copy link

Added -f flag. if the tip of your current branch is behind then it will be helpful

Added `-f` flag. if the tip of your current branch is behind then it will be helpful
@cpina
Copy link
Owner

cpina commented Oct 25, 2021

Mmmm... I'm just thinking (I haven't had time to do anything with this github-action for a while): if it's behind and it can fast-forward I think that it works without the -f. "man git-push" says:

can cause the remote repository to lose commits; use it with care.

Now the github-action can push into a directory (and leave the repository untouched) I think that this might cause problems. This is a new option after you did the PR.

Have you found some flow where you needed the -f?

@MischaPanch
Copy link

MischaPanch commented Dec 13, 2021

I only now noticed this PR. I needed a force push for my workflow and created a PR where force pushing is optional (and not default). @cpina If you are maintaining this repo, then I believe my PR supersedes this one

@cpina
Copy link
Owner

cpina commented Jan 22, 2022

I still need to look into this. Before merging code and adding features / changes I want to write tests to avoid regressions, that's why I haven't actioned it yet.

@cpina cpina linked an issue Jan 22, 2022 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Write tests
3 participants