From hesitation to collaboration: embracing GitHub in research

GitHub is an important part of the OpenSAFELY Schools infrastructure, and one which underpins transparency, reproducibility, and collaboration across teams. When we recently introduced GitHub to the TIDE team and wider Research and Best Practice team at the NIOT, we were inviting a shift in mindset, not just teaching a tool.

For many in the team, GitHub was unfamiliar territory. It wasn’t just about learning a new interface, understanding forks and branches, or remembering to commit changes. It was about embracing a new way of working: one that will help us share code securely, track changes, and strengthen our collaborative approach to research.

From hesitation to engagement

Our conversations around GitHub have been honest and revealing. Some team members have been unsure about using it as it is an unknown entity, while others have stressed the value of shared documentation and transparency. A key point was that GitHub doesn’t slow work down, it makes code accessible and supports long-term collaboration.

These reflections helped us shape the training not just around functionality, but around purpose. We weren’t just teaching GitHub, we were helping the team understand why it matters.

Training with purpose

Our sessions focused on:

• Centralised documentation: Creating a shared understanding of what we’re doing with the data.
• Code sharing: Ensuring that reproducible code can be accessed and reused after a project ends or if there is a change in the team.
• Safe practices: Reinforcing that GitHub is for code, not data - an important distinction for safeguarding sensitive information.

We also encouraged team members to explore GitHub Desktop and attend training sessions which demystified the platform and showed how it could support their work.

Cultural change, not just technical change

Introducing GitHub wasn’t just about improving workflows. It was about building trust in a new system. That meant:

• Acknowledging discomfort: Some team members were unsure or reluctant, and that was okay.
• Creating space for dialogue: We used meetings and training sessions to surface concerns and clarify misconceptions.
• Modelling the change: By using GitHub ourselves and sharing examples, we showed what good practice looks like.

Looking ahead

As OpenSAFELY Schools moves towards a secure, reproducible research platform, GitHub will be a key part of that infrastructure. But its success depends on more than technical adoption, it also depends on cultural buy-in.

We’re proud of the progress the team has made, and we’ll continue to support them as they integrate GitHub into their everyday work. Because when researchers understand the “why,” the “how” becomes much easier.