Add check that all external packages used as synced across all repositories
@IsakNaslundBh is already working on this.
Since Jun 25, 2024.
Assessment
This issue has not been assessed yet.
Description
Description:
Discussed with @adecler that we should add a check that ensures that any external package used by a project is not in conflict with the same package from a different version in a project in another repository. Could potentially be made part of the project compliance check, or turned into a completely new check.
Once implemented we should bulkrun the check across all repositories and ensure they are all in sync, and can then have the check run on PRs that are changing their exteral nuget usages in any way, either by adding a new package or changing version of an already existing one.
- Dominant language
- C#
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from BHoM/Test_Toolkit
-
type:feature
Difficulty 3/5 1-2 days Newbie friendliness 45/100
BHoM/Test_Toolkit#552 ·
-
type:bug
BHoM/Test_Toolkit#550 · 1 assignee ·
-
type:compliance
BHoM/Test_Toolkit#547 · 1 assignee ·
-
type:feature
BHoM/Test_Toolkit#530 · 3 assignees ·
-
type:feature
Difficulty 4/5 3-5 days Newbie friendliness 45/100
BHoM/Test_Toolkit#526 ·
All issues in BHoM/Test_Toolkit
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·