Skip to content
This repository has been archived by the owner on Nov 25, 2022. It is now read-only.

Discourage (prevent?) use of push --force #94

Open
salcode opened this issue Dec 26, 2018 · 1 comment
Open

Discourage (prevent?) use of push --force #94

salcode opened this issue Dec 26, 2018 · 1 comment

Comments

@salcode
Copy link
Member

salcode commented Dec 26, 2018

While we have added aliases to make it easier to use push --force-with-lease instead of push --force (see both #10 and #71), I would like go so far as to prevent push --force.

I've not determined a way to do this with a git alias (since I don't see a way to map a current command, i.e. git push, to something else).

I think the best route may be to create a bash script that runs in place of git. The script would listen for push --force and intervene in that situation, otherwise it would pass along all commands to git.
salcode added a commit that referenced this issue Dec 26, 2018
@salcode
Add bash script git-without-force.sh
c31f9c8 
This script should be executible and aliased to git.
If someone tries to use `git push --force` it prevents them, otherwise
it calls the real copy of git with the same parameters.

See #94
salcode added a commit that referenced this issue Dec 26, 2018
@salcode
Add bash script git-replacement.sh
9fae369 
By aliasing "git" to this script, we can add our own checks before
git does anything.

e.g. We can check if the user is trying to use
git push --force
and present them with an error message and explanation on why
it is a bad idea.

Once our checks are based, this script calls the real git program and
passes in the same parameters.

See #94
salcode added a commit that referenced this issue Dec 26, 2018
@salcode
Alias git to our git-replacement.sh script
584ed01 
See #94
salcode added a commit that referenced this issue Dec 26, 2018
@salcode
Add bash script git-replacement.sh
39a6c5c 
By aliasing "git" to this script, we can add our own checks before
git does anything.

e.g. We can check if the user is trying to use
git push --force
and present them with an error message and explanation on why
it is a bad idea.

Once our checks are based, this script calls the real git program and
passes in the same parameters.

See #94
salcode added a commit that referenced this issue Dec 26, 2018
@salcode
Alias git to our git-replacement.sh script
704f3c5 
See #94
salcode added a commit that referenced this issue Dec 26, 2018
@salcode
Update README.md to include push force preventaion
5634193 
See #94
salcode added a commit that referenced this issue Dec 26, 2018
@salcode
Update CHANGELOG to include push force preventation
9fa026c 
See #94
salcode added a commit that referenced this issue Dec 26, 2018
@salcode
Add bash script git-replacement.sh
c75c709 
By aliasing "git" to this script, we can add our own checks before
git does anything.

e.g. We can check if the user is trying to use
git push --force
and present them with an error message and explanation on why
it is a bad idea.

Once our checks are based, this script calls the real git program and
passes in the same parameters.

See #94
salcode added a commit that referenced this issue Dec 26, 2018
@salcode
Alias git to our git-replacement.sh script
58f9afe 
See #94
salcode added a commit that referenced this issue Dec 26, 2018
@salcode
Update README.md to include push force preventaion
88243a1 
See #94
salcode added a commit that referenced this issue Dec 26, 2018
@salcode
Update CHANGELOG to include push force preventation
e0b8130 
See #94
@salcode
Copy link
Member Author

salcode commented Dec 26, 2018

I'm testing out some code to add this git push --force prevention behavior. It is on branch sf/prevent-push-force-94.

I'll use it in my everyday use for a bit and if I'm happy with it, I'll create a PR to merge this functionality.

salcode added a commit that referenced this issue Jan 11, 2019
@salcode
Add bash script git-replacement.sh
122821c 
By aliasing "git" to this script, we can add our own checks before
git does anything.

e.g. We can check if the user is trying to use
git push --force
and present them with an error message and explanation on why
it is a bad idea.

Once our checks are based, this script calls the real git program and
passes in the same parameters.

See #94
salcode added a commit that referenced this issue Jan 11, 2019
@salcode
Alias git to our git-replacement.sh script
880dbe9 
See #94
salcode added a commit that referenced this issue Jan 11, 2019
@salcode
Update README.md to include push force preventaion
7c44b4c 
See #94
salcode added a commit that referenced this issue Jan 11, 2019
@salcode
Update CHANGELOG to include push force preventation
e11644c 
See #94
salcode added a commit that referenced this issue Jan 15, 2019
@salcode
Add bash script git-replacement.sh
2554ac7 
By aliasing "git" to this script, we can add our own checks before
git does anything.

e.g. We can check if the user is trying to use
git push --force
and present them with an error message and explanation on why
it is a bad idea.

Once our checks are based, this script calls the real git program and
passes in the same parameters.

See #94
salcode added a commit that referenced this issue Jan 15, 2019
@salcode
Alias git to our git-replacement.sh script
72d02e1 
See #94
salcode added a commit that referenced this issue Jan 15, 2019
@salcode
Update README.md to include push force preventaion
d9c0e41 
See #94
salcode added a commit that referenced this issue Jan 15, 2019
@salcode
Update CHANGELOG to include push force preventation
98f96cb 
See #94
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@salcode