+ [2020-03-05T10:42:46Z] ajnr Soliton, I have changed my current working directory to your local repositoryand then excuted the above command git rm --cached giant_file here the giant_file i sthe embeding file. i gave the path , but it is not working. i may be doing wrong somewhere
+ [2020-03-05T11:02:43Z] ajnr Soliton, Thanks - trying
+ [2020-03-05T12:47:29Z] BtbN Can I make a step in a Github workflow conditional?
+ [2020-03-05T12:47:43Z] BtbN I have a final step that pushes a built and tested Docker-Image to a registry.
+ [2020-03-05T12:48:16Z] BtbN But whenever someone forks the repo and does stuff, they get a failure e-mail for every push, because their fork obviously does not have the credentials.

message no. 177556

Posted by BtbN in #github at 2020-03-05T12:48:16Z

But whenever someone forks the repo and does stuff, they get a failure e-mail for every push, because their fork obviously does not have the credentials.
+ [2020-03-06T09:03:43Z] th_ any way to see the size of a repo?
+ [2020-03-06T10:10:04Z] R2robot du -h in your repo dir should give you an idea
+ [2020-03-06T10:25:39Z] canton7 th_, it's a tricky question to answer: a repo might be highly compressed (for efficiently transfer it over a network), or it might have removed compression in lots of places (to let you switch branches quicker without having to decompress stuff), or it might have garbage in it (because running the GC is costly). Probably the best thing is to clone
+ [2020-03-06T10:25:39Z] canton7 it with --no-hardlinks, the use du in the clone: that forces it to fully compress
+ [2020-03-06T10:26:18Z] canton7 Although that's also affected by config values like core.compression, and the ones which tell it how much effort to put into packing