pre-receive hook discussion to reject force push to git repository.

Thanks for this discussion, (https://answers.atlassian.com/questions/224620/how-to-write-a-pre-receive-hook-in-bash-or-python)

I have a python pre-receive force push reject hook in place per the thread and it works as expected.

Here is a related question:

the upload of the "soon to be rejected object" has already happened, so the object will be still in the repository on the server, right ? in that case what is the GC schedule for stash ?

2 answers

1 accepted

Hi Rajesh,

That's correct.

Current Stash relies on the auto gc built into Git, which runs intermittently depending on how many loose objects there are in Git.

At some point I imagine Stash will need to get more sophisticate about scheduling the GC. There is also an addon that lets you do it manually:

https://marketplace.atlassian.com/plugins/com.atlassian.stash.plugin.stash-git-ops-plugin

It's worth mentioning that we change the configuration of a Git repository when you create your first fork due to the fact that we are using Git alternates (a way in Git share objects between repositories). Just something to keep in mind.

Either way I probably would worry too much about that rejected object unless disk space on your Stash server is a concern?

Cheers,

Charles

Thanks and that was going to be my next question was about alternates. we were worried that in case of fork we would hit some issues with this approach and hence we disabled the forks for now, with a workaround to do a private repository with copy and go from there. (not optimal but atleast we think workable.)

the issue is that we do a fork of a repository and then in the master some one deletes the branch for e.g. then how will fork behave.? any comments ?

Hi Rajesh,

Deleting the branch should be fine - Stash forks are completely safe. But obviously the commits/blobs in the master repository will be unreferenced now, which is why we disable pruning (the cleanup part of gc) when you fork, so the repository will never shrink. We definitely plan on fixing this, but it's not trivial. For most people it's not a problem because 99% of the time commits end up on master and/or they don't use rebase.

I wouldn't be afraid of using forks unless you are expecting lots of large files to be pushed to Stash that you then reject. And even then I wouldn't be too concerned.

Cheers,

Charles

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Posted Jun 12, 2018 in Bitbucket

Do you use any Atlassian products for your personal projects?

After spinning my wheels trying to get organized enough to write a book for National Novel Writing Month (NaNoWriMo) I took my affinity for Atlassian products from my work life and decided to tr...

30,771 views 26 12
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you