New Project at work.
First commit: 'Initial commit'
Second commit: 'Refactoring'
-.-

git commit -m "Batman! (this commit has no parents)"

I'll show myself out.

Initial commit

(last commit to readme.md 1 year ago)

- initial commit

The feeling when you try to be creative on the first commit message but end up using 'Initial commit'...

That feeling when your commit title is : "initial commit" for a new project. :)

Me:
* I wanna make a website
* I'm good at backend
* I suck at frontend

Friend:
* I wanna make a website
* I suck at backend
* I'm good at frontend

Initial though: Match made in heaven
Now: FFS Wordpress is not the kind of frontend I had in mind.

git commit suicide.txt -m "It was a nice thought before it was put into action"

Method 1:
1. Read others' people answers on wk70
2. Apply
3. ???
4. Profit
Method 2:
1. cd <ProjectName>
2. git init
3. dotnet new sln
4. dotnet new console #or webapi/lib
5. code .
6. git commit -m "Initial commit"
7. git remote add origin <github link>
8. git push origin master -u
9. profit

I'm investigating PRs for a super legacy codebase. Someone else already approved the PRs -- somebody who has never even run the code or had the project set up before.

The codebase hasn't been touched in two years, and it hasn't been updated in four. It's using CoffeeScript, Node v0, Electron v0.30, and Angular 1.x. I obviously don't have a dev environment anymore, either, and my previous dev env was on Windows, so I'll have to translate my custom build utilities from batch to bash (or much more likely: node).

To make matters worse: the PRs break both the initial project setup and the project itself (NPM can no longer find some installed packages, among other problems). And. someone already merged them into master. So: fuck.

I'm going to yell at the author and tell him to fix his shit. Why? Because when I check out my last commit prior to his PRs, everything works perfectly. Surprise!

I was so done with this project two and a half years ago. I'm still so done with it. I just don't want to maintain this anymore, or honestly even look at it. I would happily rebuild the project from scratch, but updating it from the days of IE8? No way.

My first post is not a rant. This is initial commit. git push -a -muthafaka

Looking at the version history of Git (which is obviously tracked by Git), it goes all the way back to the initial commit...for some reason this blows my mind.

Someone else always have git log like this??
Or just me? 😂 ;-)

commit 6e71f545c3
Author: ShellAddicted
Date: Sat Sep 9 02undefined21 2017

it Works!!!

commit 6ac2c98bf
Author: ShellAddicted
Date: Sat Sep 9 01undefined47 2017

works more or less

commit 411b8e12
Author: ShellAddicted
Date: Sat Sep 9 00undefined00 2017

Initial state not working.

EDIT:
I just noticed that devrantron modified (bug) my rant (see the undefined in times)

When you join a new project, look at the git log, and all the commits say 'initial-commit'... 😭

Never forget how it feels to be new and overwhelmed. For every question that you ask, remember that you should eventually pay that back by answering one for someone newer than you.

I think a lot of times, once developers get enough experience, it's all too easy to judge or make fun of those who are new for something they don't know. Remember that you were there once and lend a non-judgmental helping hand!

Keep this in mind: I don't like WordPress and PHP at all!!!
So a couple of days ago my boss asked me if I could extend a custom made WordPress plugin made by our intern. First thought: sure why not? Boss says: it has to be done in less than 100 hours of work (an estimate done by my boss and the intern). Me: I can't tell you that before I have seen the code and what functionality has to be in the extension. Boss: Cool, look it over this weekend and tell me if you want to do it or not.
I looked it through and my answer will probably be: NO WHERE IN HELL am I gonna are this in less that 100 hours! 1. no tests has been performed so I have absolutely no clue if his code works.
2. variable names are mostly: $string_query (whatever that means?), $result, $string_temp and so on.
3. Methods and functions are more than 250 lines long, with shitty formatting, and more comments than code. WTF?
4. The estimate has been made by an intern and my boss (doesn't know much about programming). I haven't been consulted about it....
5. No version control. No branches, no commits other than initial commit. Great.
6. Most comments in the code just tells me what I can read from the code. What it returns and what it takes as params. Can I please know wtf your method call named $booking->run () does? I still haven't found this method in the code after 1 hour of intensively looking for it...

FFS man... Not gonna do this, even though I thought it would have been an interesting project initially.

Sorry for the long rant... I just wish the intern would have consulted me about all this shit, since he obviously have bad practices. *sigh*

1. Get an idea
2. Plan the structure to use overengineered solutions
3. $ git init
4. Setup the barebones
5. $ git commit -am "initial commit"
6. Forget the project for the next several months, until another idea pops out and you visit your github to setup a repo for the new project and rediscovers this miserable project's repo
7. Back to 1, repeat

rm -rf *
git add .
git commit -m "Initial commit"
git push -f

The most awkward thing that can happen to a programmer.
Multiple Initial Commits

FML..

I worked directly in my Github repo folder while working on a project (don't ask me why). I did my initial commit with all my code from the start until 5 hours ago. I never pushed.. A minute ago, I checked my commit and noticed that there were DB credentials in one of the files. So.. Smart me.. "revert commit"..

Result. Everything got deleted except my node_modules folder and the readme file.. I lost everything.. Fuck me, I'm going home..

Please, someone.. Can I get these files back via git or something? Can't find anything in in the history..

Just when I thought js/ts is a mess with its npm, I ran into GO

$ xk6 build --with gitlab.com/<...>
smth wrong with module name

*fixes module name*
$ git push
$ xk6 build --with gitlab.com/<...>
smth wrong with module name
*go pulls initial commit instead of the last one*

$ go clean [or wtv it's called]
$ xk6 build --with gitlab.com/<...>
smth wrong with module name
*go pulls initial commit instead of the last one*

$ cd /tmp
$ xk6 build --with gitlab.com/<...>
OK

oh well... I guess this is how it's gonna be

Question about git: What do you do when you have a massive pull request? This guy I work with made a PR with 13k files out of which 11-12k is basically HTML's that should have been added as an initial commit, and remaining ones are actual files that we worked on. Should I ask him to somehow split his work in two parts?

New favorite commit Message:
"Initial force commit"

When you teach people how to code as much as I do, having to explain why things like this are so wrong over and over again starts to make you die inside.

the feeling when you pick up your AOP library that you've last updated on 10/Oct/2016, has single commit "Initial commit (MVP)", absolutely no docs and you touch a couple of places for 10-15 minutes and boom you get everything working ...

Thanks former self, thank you for actually being more or less logical, thinking and did coding like a boss..

Here we go another with another pet to get refactored and revived

Exercise app got it all planned out in my head (well sort of). All day at work I'll be getting ideas on how id make it.

Day ends and I feel motivated to work on it all the way home. Get in make a cup of tea boot pc create a project do initial commit to git.

And nothing. Motivation dead ability to think gone. So I'll sit there sipping my tea trying to get motivated.

Eventually I'll close it down and get motivation to start it again at 4am which isn't an ideal time to start a project.

In a long git project what u find commit message
"Minor fixes" or "minor code updated"

At the first commit you will find "initial code"

Agree??

In a world brimming with enticing investment opportunities, it is crucial to tread carefully. The rise of digital currencies has attracted many eager investors, but along with this excitement lurk deceitful characters ready to exploit the unsuspecting. I learned this lesson the hard way, and I want to share my story in the hopes that it can save someone from making the same mistakes I did.

It all began innocently enough when I came across an engaging individual on Facebook. Lured in by promises of high returns in the cryptocurrency market, I felt the electric thrill of potential wealth coursing through me. Initial investments returned some profits, and that exhilarating taste of success fueled my ambition. Encouraged by a meager withdrawal, I decided to commit even more funds. This was the moment I let my guard down, blinded by greed.

As time went on, the red flags started to multiply. The moment I tried to withdraw my earnings, a cascade of unreasonable fees appeared like a thick mist, obscuring the truth. “Just a little more,” they said, “Just until the next phase.” I watched my hard-earned money slip through my fingers as I scraped together every last cent to pay those relentless fees. My trust had become my downfall. In the end, I lost not just a significant amount of cash, but my peace of mind about $1.1 million vanished into the abyss of false promises and hollow guarantees.

But despair birthed hope. After a cascade of letdowns, I enlisted the help of KAY-NINE CYBER SERVICES, a team that specializes in reclaiming lost funds from scams. Amazingly, they worked tirelessly to piece together what had been ripped away, providing me with honest guidance when I felt utterly defeated. Their expertise in navigating the treacherous waters of crypto recovery was a lifeline I desperately needed.

To anyone reading this, please let my story serve as a warning. High returns often come wrapped in the guise of deception. Protect your investments, scrutinize every opportunity, and trust your instincts. Remember, the allure of quick riches can lead you straight to heartbreak, but with cautious determination and support, it is possible to begin healing from such devastating loss. Stay informed, stay vigilant, and may you choose your investment paths wisely.

Email: kaynine @ cyberservices . com