Skip to content

Activate custom aliases in VSCode automatically#246

Open
tomschr wants to merge 1 commit intomainfrom
toms/vscode-acivate-aliases
Open

Activate custom aliases in VSCode automatically#246
tomschr wants to merge 1 commit intomainfrom
toms/vscode-acivate-aliases

Conversation

@tomschr
Copy link
Copy Markdown
Contributor

@tomschr tomschr commented May 1, 2026

Situation

When opening a new terminal under VSCode, it sources .venv/bin/activate and activates the virtual Python environment. However, we need to manually source our own aliases. This is a bit inconvenient as you don't have access to this alias (and neither your AI bot has that).

Proposed solution

This fix activates our own custom aliases in devel/activate-aliases.sh. It works for Linux and MacOS.

Alternatives

An alternative way would be to create a docbuild.code-workspace file and add the additions under a settings key. That may be even the more portable solution.

When opening a new terminal, VSCode sources `.venv/bin/activate` and
activates the virtual Python environment. However, we need to manually
source our own aliases.

This fix activates our own custom aliases in `devel/activate-aliases.sh`.
It works for Linux and MacOS.
@tomschr tomschr requested a review from sushant-suse May 1, 2026 08:24
@tomschr tomschr added the area:infrastructure Related to GitHub, project structure, project maintenance etc. label May 1, 2026
@tomschr tomschr marked this pull request as ready for review May 1, 2026 08:24
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 1, 2026

Coverage Report

For commit 89eabb8

Click to expand Coverage Report
  Name                                           Stmts   Miss Branch BrPart  Cover
  --------------------------------------------------------------------------------
+ src/docbuild/models/deliverable.py               180      1     22      0  99.5%
+ src/docbuild/cli/cmd_check/process.py             58      0     22      1  98.8%
+ src/docbuild/models/manifest.py                  111      1     12      1  98.4%
+ src/docbuild/utils/pidlock.py                     79      1     14      1  97.8%
+ src/docbuild/cli/cmd_config/list.py               26      0      8      1  97.1%
+ src/docbuild/cli/cmd_validate/process.py         178      5     52      4  96.1%
+ src/docbuild/cli/callback.py                      35      0     10      2  95.6%
+ src/docbuild/utils/concurrency.py                 69      3     18      1  95.4%
+ src/docbuild/cli/cmd_cli.py                      110      3     16      3  95.2%
- src/docbuild/config/xml/stitch.py                 47      5     12      0  88.1%
- src/docbuild/cli/cmd_metadata/metaprocess.py     215     26     66     13  82.6%
- src/docbuild/cli/cmd_config/validate.py           21      2     12      3  78.8%
- src/docbuild/cli/cmd_check/__init__.py            18      5      2      0  65.0%
- src/docbuild/cli/cmd_build/__init__.py            13      5      0      0  61.5%
- src/docbuild/cli/cmd_metadata/__init__.py         27     10      2      0  58.6%
  --------------------------------------------------------------------------------
+ TOTAL                                           3068     67    746     30  97.0%
  
  47 files skipped due to complete coverage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:infrastructure Related to GitHub, project structure, project maintenance etc.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants