adding in an rst linter#796
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #796 +/- ##
==========================================
+ Coverage 82.03% 82.09% +0.05%
==========================================
Files 67 67
Lines 3736 3736
==========================================
+ Hits 3065 3067 +2
+ Misses 671 669 -2
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
|
@ilaflott Qhat did you change in the last commit? I can't tell |
i updated your branch via |
|
Thanks! |
…docs dependency. Also updating rst linter workflow to install via pip without a requirements.txt.
…g builder build error
ilaflott
left a comment
There was a problem hiding this comment.
works! thank you. ponder optimizations as you feel necessary
There was a problem hiding this comment.
this could actually be even more minimal, avoiding cloning CatalogBuilder-
steps:
- name: Code Checkout
uses: actions/checkout@v4
- name: Prepare Python
uses: actions/setup-python@v5
with:
python-version: '3.11'
cache: 'pip'
- name: Install doc8
run: pip install doc8
- name: Lint RST files
working-directory: ./fre-cli
run: doc8 *
Removed external catalogbuilder checkout and installation steps. Added doc8 installation for RST linting.
Removed working-directory for Python requirements installation.
Describe your changes
Issue ticket number and link (if applicable)
This PR fixes #810
Checklist before requesting a review
Note: If you are a code maintainer updating the tag or releasing a new fre-cli version, please use the
release_procedure.mdtemplate. To quickly use this template, open a new pull request, choose your branch, and add?template=release_procedure.mdto the end of the url.