all 73 comments

sorted by: hot top controversial new old
[–] 38 points 4 months ago (2 children)

You don't just write your entire project, then make your first commit?

/j

  • source
  • hideshow 2 child comments
  • [–] 37 points 4 months ago (10 children)

    Yeh I use git (git commit --amend)

  • source
  • hideshow 10 child comments
  • [–] 5 points 4 months ago*

    git commit --amend --no-edit and git push --force-with-lease

    No-edit skips opening an editor for the commit message and just reuses the same message.

    Force-with-lease will force push but only if your local is not missing commits that remote has. Ie other people haven't pushed anything since you last pulled.

  • source
  • parent
  • [–] [S] -1 points 4 months ago (7 children)

    Would this also trigger (git rev-parse) to change? I have CI/CD listening to changes on the master branch

  • source
  • parent
  • hideshow 7 child comments
  • [–] 3 points 4 months ago (4 children)

    Work off the master branch first, don't push to prod until you're ready to

  • source
  • parent
  • hideshow 4 child comments
  • [–] [S] 1 point 4 months ago (3 children)

    Well, prod is luckily the people I have next room. I made the setup so changes get uploaded quickly. I could do branches and all that stuff?

    Yeah, but i'd rather not work to work and just get it out the door. What my setup is for is that changes get pulled off the master branch and deployed without an apparent interruption of service.

    I see collaboration tools just the same as abstractions, you don't use them just to use them. They need to solve a problem.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 4 months ago (2 children)
  • [–] [S] 2 points 4 months ago (1 child)

    It's a collaboration tool and i'm not collaborating with anyone so why'd I bother going through the extra bells and whistles?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 4 months ago (1 child)

    Well, there's your problem.

    Get yourself a nice button/endpoint you can hit to trigger CI/CD that way instead

  • source
  • parent
  • hideshow 1 child comment
  • [–] [S] 1 point 4 months ago

    You're saying it's a problem but i'm not really reading why. While the idea of a massive button to push changes is fun having the master branch be production is a concrete idea i've grown fond of, iteration is fast, both at testing and deployment.

  • source
  • parent
  • [–] 68 points 4 months ago (1 child)

    👏 Learn 👏 to 👏 squash 👏 those 👏 commits 👏

  • source
  • hideshow 1 child comment
  • [–] 26 points 4 months ago (32 children)

    rebase & fixup or reset are your friends

  • source
  • hideshow 32 child comments
  • [–] 14 points 4 months ago (14 children)

    I love editing history. Fix the bug in the change that introduced it!

  • source
  • parent
  • hideshow 14 child comments
  • [–] 15 points 4 months ago (13 children)

    Then force-push, and fuck up someone's day!

  • source
  • parent
  • hideshow 13 child comments
  • [–] 15 points 4 months ago* (11 children)

    git branches are free
    work in your tree
    til the changes are ready
    300 git push --force-with-lease a day and nobody mad

  • source
  • parent
  • hideshow 11 child comments
  • [–] 2 points 4 months ago (8 children)

    Continuous integration is better. Fight me

  • source
  • parent
  • hideshow 8 child comments
  • [–] 6 points 4 months ago (7 children)

    Nothing about continuous integration prevents you from using a branch to prepare your changes.

  • source
  • parent
  • hideshow 7 child comments
  • [–] 2 points 4 months ago* (last edited 4 months ago) (6 children)

    Yes, if you use feature branches its literally not continuous. It’s adjacent though.

    Continuous Integration is a software development practice where each member of a team merges their changes into a codebase together with their colleagues changes at least daily

    Meaning everything is in a version controlled mainline

    People disagree about what CI is, but that’s the definition i subscribe to

  • source
  • parent
  • hideshow 6 child comments
  • [–] 2 points 4 months ago (5 children)

    So does everyone work directly on main all the time? Do all of you work on the same project or are there multiple with one person per project? How do you work around the broken code your coworker just pushed so you can finish your tasks?

  • source
  • parent
  • hideshow 5 child comments
  • [–] 3 points 4 months ago* (3 children)

    Yea you always work on main on the same project.

    You don’t push broken code. You always need to keep mainline healthy

    It takes some special considerations, but the benefits are great.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 4 months ago (1 child)

    so when something breaks both devs, the one who made the previous change and the person pushing new, have to work together to solve the issue? no PRs or is everything a fork? do you revert and rebase every change?

  • source
  • parent
  • hideshow 1 child comment
  • [–] [S] 1 point 4 months ago

    I personally make feature files. So if i'm working on FactorySeederModemLookupVector.ts someone elses could work on ☝️🥵🙏.php without bothering each other. Tho, my collabs have been ones with a LOT of communication.

  • source
  • parent
  • [+] [S] -16 points 4 months ago (16 children)

    I personally don't really care for the meaningful messages or a pretty log. I only see these myself.

  • source
  • parent
  • hideshow 16 child comments
  • [–] 8 points 4 months ago (2 children)

    Then why are you using source control at all? You can manually copy the directory and name it "— Copy".

  • source
  • parent
  • hideshow 2 child comments
  • [–] 7 points 4 months ago (1 child)

    Future you might not think the same

  • source
  • parent
  • hideshow 1 child comment
  • [–] [S] -1 points 4 months ago

    Should I find a problem solved by me adding commit messages i'll gladly do it. I use stuff as I find an usecase for it. Atm, i'm completely alone so i've 0 need to write up what my changes do. It personally gets in the way of quickly iterating and then testing.

  • source
  • parent
  • [–] 19 points 4 months ago (9 children)

    And clearly as a Windows developer, you hate yourself and don't believe you deserve nice things, so it all checks out.

  • source
  • parent
  • hideshow 9 child comments
  • [+] [S] -6 points 4 months ago (8 children)
  • [–] 5 points 4 months ago (3 children)

    I'm very confused haha. didn't you say this code was just personal code? or that it was just for yourself? If you're at a job why are you committing like this?

    in any case, I'm sorry for the absolute crazy amounts of hate you're getting for using windows. I do highly recommend trying out linux though. unless you're doing cad or 3d modeling, you will likely have zero issue using it.

  • source
  • parent
  • hideshow 3 child comments
  • [–] [S] -2 points 4 months ago (2 children)

    I'm the only programmer at the company. It's a closed source solution for very specific needs. So I only answer to myself and I don't have a need to explain (to myself) what I did in a particular commit and if I ever need to check the commit history I can just check a particular files history, not going commit by commit. I never said it was personal code. I said "don't code alone". I use linux at home, the server hosting the code commits is linux, the scripts listening to new commits are in bash.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 4 months ago (2 children)

    With my salary, I am boss of my OS. I tell my boss, “you really want me working on that pile of shit? Okay, it’s your time.”

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] -1 points 4 months ago (1 child)

    I didn't make this post to defend someone elses decision and all this thread is doing is assume shit because I got to use windows. Yes, composer takes ages to optimize the autoloads on windows. I know.

    You're all just being insufferable to someone forced to use it.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 24 points 4 months ago (5 children)
  • [–] 7 points 4 months ago (4 children)
  • [+] [S] -6 points 4 months ago (3 children)

    Has your real dev commits gotten you a real dev job? You seem to be looking for a job offer on your mastodon since february and i'm worried for you.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 6 points 4 months ago* (last edited 4 months ago) (2 children)

    I'm not sure if any of those commits did, but I worked 2 years doing Haskell backend and jQuery+Bootstrap frontend for Masterword. Before that I did some work for Wire: https://github.com/wireapp/wire-server/commits?author=stephen-smith Before that, I worked at TGCS for nearly a decade.

    But, right now I am still looking for work. I've actually been looking since April 2025 when my time at Masterword ended, but I did update my "hire me" posts back in February because my living situation changed, opening up more opportunities. Originally I needed something remote so I could continue to take care of my father (RIP), now relocation is certainly an option.

    If anyone reading this has a position available, or is just curios, my current resume public: https://docs.google.com/document/d/1ORf48b557nK0gYI4h6J0xP7nzOVRoqtOogYsukUMREU

  • source
  • parent
  • hideshow 2 child comments
  • [–] 20 points 4 months ago

    A dev on windows? Of course that's your git log!

  • source
  • [–] 16 points 4 months ago

    Looks like a normal branch where someone debugs some GitHub workflow.

  • source
  • [–] 14 points 4 months ago (1 child)

    Is it humor because we make fun of you?

  • source
  • hideshow 1 child comment
  • [Test] around and find out

  • source
  • [–] 13 points 4 months ago

    You need to learn refactoring/squashing

  • source
  • [–] 12 points 4 months ago

    I cannot give you a 100% for consistency. You have three inconsistent check in messages: 'tet', 'FueraEstanciaRowRename', and 'Revert "test"'. You must be uniformly informative with your messages.

  • source
  • [–] 6 points 4 months ago

    nonsense, I would never use windows

  • source
  • [–] 6 points 4 months ago

    I see I'm not the only one fighting with CI/CD pipelines.

  • source
  • [–] 6 points 4 months ago

    Me when learning GH Actions/CI/CD

  • source
  • [–] 4 points 4 months ago

    well yeah, in an enterprise project we would say "chore(test)". Semantic release ftw!

  • source
  • [–] 4 points 4 months ago

    my private repo is filled with "stuff", "more stuff", "new stuff", "changes" commits.

  • source
  • [–] 3 points 4 months ago (4 children)

    Small incremental changes are good.

  • source
  • hideshow 4 child comments
  • git rebase -i [hash of your first commit]

  • source