The-Strategy-Unit / The-Strategy-Unit/data_science

Learnings from Air adoption

Open
#447 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

section: blogs section: style guide
Dominant language
Jupyter Notebook
Stars
11
Forks
5
Avg merge
5h 34m
Merged PRs (30d)
1

Description

Switching to Air (and jarl) is good because standards, etc, also Air is fast (🦀):, etc. But also learning moments like some team members can't install these (so forced-format Action might be useful) and use of .git-blame-ignore-revs file.

@Lextuga007 chatted about this.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the Air and jarl adoption notes in this issue, including the proposed forced-format Action and the .git-blame-ignore-revs file. Clarify with the maintainers whether the outcome should be documentation, an Action, or repository configuration, then define what completed adoption guidance would include.

Written by the indexing model from the issue text.

Assessment

Tech stack
git
Domain
documentation, tooling
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.