vscode-extensions.teros-technology.teroshdl: init at 7.0.3

[lheintzmann1]

vscode-extensions.teros-technology.teroshdl: init at 7.0.3
Release: https://github.com/TerosTechnology/vscode-terosHDL/tree/latest

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• Nixpkgs 25.11 Release Notes (or backporting 24.11 and 25.05 Nixpkgs Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
• NixOS 25.11 Release Notes (or backporting 24.11 and 25.05 NixOS Release notes)
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[drupol]

Hello !

Thank you for your first PR to this project.

Here's my feedback:

• This PR must only contain 2 commits:
• 1 for adding you in the maintainer list (This commit must be the first commit in the PR)
• 1 for adding the extension
• Each VSCode extension lives in their own file. Try to get some inspiration from this PR #406449
• Rewriting the Git history implies using git push --force (or an equivalent command if you're using another Git frontend like jujutsu).
  • Don't recreate a new PR, do everything in this PR
  • It is recommended to set your PR in draft mode before doing the rebase operation to prevent mass-pinging maintainers in case of issue
• If you're looking for some help on how to properly format your commits, have a look at the Contributing guide, or simply look at the existing merged PR in the project.

Let me know if you need some assistance,

Good luck!

[lheintzmann1]

@drupol Hello, Thank you for your help !
I think it's good now. (I had to redo a force push a second time because there was a syntax error, I hope it won't be a problem)

[drupol]

💯 ! Thank you !