you are viewing a single comment's thread
view the rest of the comments
[–] [S] -1 points 1 month ago (3 children)

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

  • source
  • parent
  • hideshow 6 child comments
  • [–] 7 points 1 month ago* (last edited 1 month ago) (1 child)

    When you have to amend a commit that you have already pushed you have to force push the amendment. That should then trigger the Pipeline

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 1 month ago (1 child)

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

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 1 point 1 month ago (1 child)

    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 2 child comments
  • [–] 3 points 1 month ago (1 child)
  • [–] 1 point 1 month 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 2 child comments
  • [–] [S] 1 point 1 month 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