(I upvoted you, for asking the real questions, but to answer)

> Where do you keep Issues,

Youtrack

> Pull Requests,

Gerrit, it's way better for code review

> Wikis,

Also Youtrack, but other software exists that's specific for this, I have seen Confluence used a lot and while I don't recommend: that's usually the case.

> Discussions,

As far away from code as possible, right now it's Zulip

> project boards,

Youtrack, though usually in companies they use Jira for this.

> and everything else? (rhetorical question.)

In proper tools that are designed to solve a specific need, not try to do everything: badly.

--

Now, a sane person will respond to me with the fact that I haven't removed any single points of failure, I've actually just added more of them. They'd be right! The differences is that it makes the stack a bit more flexible and composable. Migration of, say, the Wiki, doesn't make major issues because it's already somewhat decoupled.

> In proper tools that are designed to solve a specific need, not try to do everything: badly.

And when you want to search for that one thing that you know got documented somewhere, but can't remember where, how many systems do you have to search?

That's one of the reasons I like the code, issues, docs (code or wiki depending), and discussions all in the same repo.

Not to be confused with Chat, which is more ephemeral, and is, for us, in Slack. But we have to be mindful of chat discussions that turn substantive and make sure we copy that info to a Discussion in the repo (which can be annoying to do and annoying when it's not done).

I don’t get it. That’s a lot of failure points to incur in the name of flexibility.