What would an inclusive curriculum look like in a computer science course?
This is an interesting question. The program I am doing most of my teaching in has recently been faced with a similar question (due to comments of an external evaluation), and I can't say we have come up with a satisfying solution yet.

Here are some pointers (in no particular order) that have come up in our discussion:


For exam tasks / homework descriptions: evaluate critically if your tasks (or rather, their descriptions) carry bias. Naturally, you want to avoid the cool developer being called Bob and the silly user Alice or Ahmed, but it goes deeper than that. For example, in an Intro to Programming exam I was giving many years back the task was to model and implement a simulation of a game of football/soccer (the assumption here being that the majority population - white, male college kids in Europe - would be intimately aware of the rules and have an easy time conceptualizing the task). As it turns out, those that did not fall into the majority population (some women, foreign students) did worse on this task, presumably because they needed to spend a lot more brain cycles even understanding the game they were supposed to simulate.
For deadlines: consider that some students may not be able to, if need be, work through the night or the weekend. It's easy to think that a deadline Sunday evening is not a big deal if you think of your students as a homogenious mass of 20-year-olds with no other obligations than to study, but if one of your students is a father / mother of two, or working on the weekend to sustain themselves, the story becomes different.
For extra-curricular activities: the same is also true for extra-curriculars. If at all possible schedule attractive extra-curriculars (e.g., Hackathons, job fairs, whatever your university does) in a way that they can also be attended by people outside the majority population.
For social events: the same applies to social events. Make sure that social events, to the extent possible, not only cater towards the majority population. For instance, when I studied, a lot of the student social events boiled down to "find an excuse to drink", and basically all conversation was in the local language. Both of this together unsurprisingly meant that foreign students, especially Islamic students, never showed up.
Avoiding "hidden knowledge": in many universities and courses, there are official rules and "unspoken rules". For example, a teacher may say that students are expected to learn the entire book, but well-connected members of the majority population know from previous years that in reality most of the questions are about Chapters 3-8. Given that (some) minorities are less well-connected than the majority population, these constructions can disadvantage these students severely.
Diversity of TAs: ensure that not all TAs are always from the majority population (i.e., ensure that there is some amount of representation of non-majority students). This may need active steering, because if you just take the first 5 qualified students, you may easily end up with only students from the majority population (because they are more, because they are better-connected, and because a lot of TA contracts are written in a way to appeal to 20-year-olds). 


To summarize: keep in mind that some of your students may have a different cultural background, different life constraints, different priorities, or different access to "common knowledge". Try to level the playing field as well as you can.