Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 24-diagnosing-issues-improving-robustness.md #376

Merged
merged 2 commits into from
Oct 25, 2024
Merged

Update 24-diagnosing-issues-improving-robustness.md #376

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
291d419
Update 24-diagnosing-issues-improving-robustness.md
jreeve-nv Aug 29, 2024
2d0831a
🐛 Remove creation and reference to the superfluous pylint-ci branch
bielsnohr Oct 21, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 1 addition & 9 deletions _episodes/24-diagnosing-issues-improving-robustness.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -742,15 +742,7 @@ you may cause yourself some trouble which may be difficult to trace).
It may be hard to remember to run linter tools every now and then.
Luckily, we can now add this Pylint execution to our continuous integration builds
as one of the extra tasks.
Since we're adding an extra feature to our CI workflow,
let's start this from a new feature branch from the `develop` branch:

~~~
$ git switch -c pylint-ci develop # note a shorthand for creating a branch from another and switching to it
~~~
{: .language-bash}

Then to add Pylint to our CI workflow,
To add Pylint to our CI workflow,
we can add the following step to our `steps` in `.github/workflows/main.yml`:

~~~
Expand Down