@FrailLeaf@Inginsub No, it's a fucking mess with almost a dozen cherrypicks and a few other commits that resolve resulting code errors, probably also with broken tests.
@FrailLeaf@Inginsub If they don't change the same parts of code, it's only a matter of a git pull. Otherwise might spend a few minutes resolving merge conflicts.
@FrailLeaf@Inginsub@mint i try. but I don't know Elixir so it's just a lot of trial and error (hence why those commits are so gross) and i'm too lazy to set up a dev instance/local instance so I just use varis as the test ground :azuki2:
@mint@Inginsub@FrailLeaf >its link is just hidden behind seven menus. it's in the place the pleroma fe puts it :gura_what: >Suddenly I don't feel as self-conscious about quality of commits. I don't know shit about Elixir :azuki_nod19:
@Halo@Inginsub@FrailLeaf While I do have test instance, the habit of commiting minor changes, sending then right to prod and then immediately commiting the fixes for those changes stays the same.
@s8n@Inginsub@FrailLeaf@Halo It's that way with any other language that isn't some low-level bytesex. Just look at the code, guess what it does, copy a bunch of snippets while changing some variables and inputs, bing if something goes wrong. Enough to hack some existing program into doing what you want.
@mint@Inginsub@FrailLeaf i just use the git so i don't have to edit stuff on command line. it's a lot easier to push n pull than write all this directly onto the prod build. If I had a local test instance the commits would probably be cleaner but... that's a lot of effort.
people shouldn't be using the horrible things I mangle together anyways. Stick to the actual developers :jahy_sick: