Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added simple binary zip containing a working version of DBP built on …
…09/02/16
- Loading branch information
3c6d83b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey Lee,
Be careful of sticking binaries like this in the repo. Even if you delete/replace them later they stick in git history forever. So everyone cloning the repo in the future would also have to download this binary as well.
A better option might be to create a release and attach the file to that. This doesn't commit the file into git so shouldn't add any bloat.
3c6d83b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good advice. Binary now on release system, deleted binary from repo area, hopefully bloat averted (unless there is a special 'perma-delete' option on GITHUB to eradicate it from history :)
3c6d83b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, cheers Lee!
Unfortunately, the file is still attached to that old commit. So the only way to remove it completely would be to reset the master branch to the state it was in before the commit was made.
These commands should do the trick:
Use
git reset
with caution though. It's usually fine to do this for a commit that was added a few minutes ago, but if someone else had cloned those commits, removing them can be really confusing for their git client.3c6d83b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First line worked, second line produced the error shown here:
I use SourceTree for GUI management of GITHUB. Is there a visual way to do the above :)
3c6d83b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops, it should've been: