Here’s the law if you’re interested in learning about it: https://www.uscis.gov/policy-manual/volume-12-part-h-chapter-3

It’s pretty easy to understand. It depends on a few different things - you can be born to a US mother and not be a citizen, or to a US father and get citizenship through him. It depends on marriage status and there are different residency requirements for different situations. Those requirements are different depending on which parent is the US citizen too.

Not to be rude, but where did you get that info? It isn’t correct. Doesn’t it sound a little too oversimplified for something like birthright citizenship laws in the US?

The mother or the father, and it depends on circumstances. The rules are more strict when the father is the US citizen.

I set up a monorepo that had a library used by several different projects. It was my first foray into DevOps and we had this problem.

I decided to version and release the library whenever a change was merged to it on the trunk. Other projects would depend on one of those versions and could be updated at their own pace. There was a lot of hidden complexity and many gotchas so we needed some rules to make it functional. It worked good once those were sorted out.

One rule we needed was that changes to the library had to be merged and released prior to any downstream project that relied on those changes. This made a lot of sense from certain perspectives but it was annoying developers. They couldn’t simply open a single PR containing both changes. This had a huge positive impact on the codebase over time IMO but that’s a different story.

How is it done at Meta? Always compile and depend on latest? Is the library copied into different projects, or did you just mean you had to update several projects whenever the library’s interfaces changed?

Can you explain a bit more?