Im trying to learn git. See if this is correct: Im developing a store API. So I branch two times, client-branch and sales-branch (emulate that two persons are working on these two domains), write and pass tests for both branches then merge to main? Is this how a branching would look like irl?
Also what would be the production, develop and stagging branches?
Suppose my API example.
>production branch This is the API that access the clients and sales domain and it is currently my v1. Its been deployed and up. >develop branch This is where the devs are implementing access to the products domain. When ready, this will be deployed and now the API is v2. >stagging branch WTF is this?
Also would the addition of a new domain require the api to be in v2 now? I mean, changing the endpoints? Or just if the access to what is v1 changed?
I'm trying to update an Android 12 app and keep getting 'App not installed as package appears to be invalid'. When I try to install it via a different installer, it says that it can't 'downgrade' the app without first uninstalling it and losing all my data. The version I want to install is definitely newer, and I've tried getting the APK from multiple sources.
Is there any way around this that lets me keep my data? Specifically, it's a mobage that I've been playing for years and managed to lose my recovery code for (and now can't login and get the code). I haven't spent a single cent on the game but I'd rather keep my rare shit.
>client-branch and sales-branch The structure of an API evolves over time, so in a few years you'll have v1, v2, ... exposed at the same time. This is because consumers of your APIs do not update in lockstep, some don't ever update. Now all these versions are in production simultaneously, and any changes need to be contained to the respective API version (say a security patch on v2 does not need to be applied on v1). This means you need to have a branch for every version you're maintaining, growing directly from master, and then further branches growing from each version branch (for new features and patches). Think of it as a tree: once a branch splits from the trunk (master), it continues in its own direction and grows other branches and leaves. It shares history with master only up to the branching point, and then diverges forever. I highlighted this on pic related, as it is characteristic for APIs. Söydevs nowadays only care about the latest version and they stop maintaining older releases, but you don't have this luxury with APIs.
TL;DR: no, your branches will initially be short-lived and look like "implement-authentication", "update for new DB schema", and so on. They will all fold into master until you add a major branch like v1, which will then grow its own short-lived branches.
what are these little tooless rubber stopper things called? Im hoping there's a way to replace them since they all hardened and crumbled away, but the drive cages are still good
Yes. Web services visibly track you across websites when you are at home. They just compare visits by the IP address. This is not possible when you use the private relay.
So far Apple is not in the advertisement networks. But they have so much information on people thanks to iPhones. Can they be trusted in the future? 9to5mac.com/2022/07/29/app-store-ads-expanding/
Lucas Cook
What do you plan to do with a VPN?
Joseph Parker
grommets? and good luck finding new ones because there's no standard for them and cunts change how they do shit all the time and never keep any spare stock and the few ones people sell on ebay cost an arm and a leg
t. guy that tried to find some for lenovo trays
Angel Anderson
Thanks. In this case, what would be deployed up and running? The release only. right?
Main branch act likes a backup?
Evan Morales
I'm new to linux and decided to install kde (plasma) when I read my os can have several desktop environments. I didn't know it would install almost a thousand fucking packages.. It's slow to boot also.
Is there a clean way to undo the install and remove everything it installed also (only). I don't want to break the system.
Gabriel Roberts
>I know we can use transparency, but that's cheating. Is it though? The image file isn't any bigger. Symmetrical oblong images are one thing, but how do you determine a reasonable 'center' for any weird blotch shape? Why not just specify a box around it at that point?
Nathaniel Williams
You can always install extra stuff without breaking. >I didn't know it would install almost a thousand fucking packages Extra info? If you start from a barebones system that does nothing but boot to console, you can easily except a thousand packages to get to a full blown DE. (wasn't modularity a good thing?)
Jason Flores
depends on the distro, what distro do you use?
Gavin Smith
I am talking about round images only.
Zachary Robinson
What advantage would round images offer to justify the code bloat?