Skip to content

Commit 460c96e

Browse files
Update: [AEA-6018] - adds new doc + converting logic (#206)
## Summary **Remove items from this list if they are not relevant. Remove this line once this has been done** - Routine Change - ❗ Breaking Change - 🤖 Operational or Infrastructure Change - ✨ New Feature - ⚠️ Potential issues that might be caused by this change ### Details Add any summary information of what is in the change. **Remove this line if you have nothing to add.** ## Pull Request Naming Pull requests should be named using the following format: ```text Tag: [AEA-NNNN] - Short description ``` Tag can be one of: - `Fix` - for a bug fix. (Patch release) - `Update` - either for a backwards-compatible enhancement or for a rule change that adds reported problems. (Patch release) - `New` - implemented a new feature. (Minor release) - `Breaking` - for a backwards-incompatible enhancement or feature. (Major release) - `Docs` - changes to documentation only. (Patch release) - `Build` - changes to build process only. (No release) - `Upgrade` - for a dependency upgrade. (Patch release) - `Chore` - for refactoring, adding tests, etc. (anything that isn't user-facing). (Patch release) If the current release is x.y.z then - a patch release increases z by 1 - a minor release increases y by 1 - a major release increases x by 1 Correct tagging is necessary for our automated versioning and release process. The description of your pull request will be used as the commit message for the merge, and also be included in the changelog. Please ensure that your title is sufficiently descriptive. ### Rerunning Checks If you need to rename your pull request, you can restart the checks by either: - Closing and reopening the pull request - pushing an empty commit ```bash git commit --allow-empty -m 'trigger build' git push ``` - Amend your last commit and force push to the branch ```bash git commit --amend --no-edit git push --force ``` Rerunning the checks from within the pull request will not use the updated title.
1 parent 09cd766 commit 460c96e

6 files changed

Lines changed: 1614 additions & 36 deletions

Makefile

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -128,8 +128,19 @@ cdk-diff:
128128
cdk-watch:
129129
./scripts/run_sync.sh
130130

131-
sync-docs:
131+
sync-docs:
132132
./scripts/sync_docs.sh
133133

134+
convert-docs:
135+
poetry run python scripts/convert_docs_to_markdown.py
136+
137+
convert-docs-file:
138+
@if [ -z "$$FILE" ]; then \
139+
echo "usage: FILE=your_doc.pdf make convert-docs-file"; \
140+
exit 1; \
141+
fi
142+
poetry run python scripts/convert_docs_to_markdown.py --file "$$FILE"
143+
144+
134145
compile:
135146
echo "Does nothing currently"

poetry.lock

Lines changed: 1287 additions & 34 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

pyproject.toml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ repository = "https://github.com/NHSDigital/eps-assist-me"
1010
package-mode = false
1111

1212
[tool.poetry.dependencies]
13-
python = "^3.13"
13+
python = "^3.14"
1414

1515
[tool.poetry.scripts]
1616

@@ -27,6 +27,7 @@ rich = "^14.1.0"
2727
pytest-mock = "^3.15.1"
2828
pytest-cov = "^7.0.0"
2929
moto = {extras = ["ssm"], version = "^5.1.17"}
30+
markitdown = {extras = ["pdf", "docx", "pptx", "xlsx"], version = "^0.0.2"}
3031

3132

3233
[tool.poetry.group.slackBotFunction.dependencies]
44.9 KB
Binary file not shown.

0 commit comments

Comments
 (0)