endjin / dotnet-adr

A cross platform .NET Global Tool for creating and managing Architectural Decision Records (ADRs).

dotnet adr - Make Future You Thank Past You

A cross platform .NET Global Tool for creating and managing Architectural Decision Records (ADR).

TLDR;

Architectural Decision Records (ADRs) are simple Markdown documents used to record technical choices for a project by summarizing the context, the decision, and the consequences. dotnet adr is a tool and a bundle of the most common ADR templates you can use to create and maintain ADRs in your solution.

Install using:

dotnet tool install -g adr

Install the default ADR templates using:

adr templates package set adr.templates

adr templates package install

Create a new ADR using:

adr new <TITLE>

Table of Contents

• dotnet adr - Make Future You Thank Past You
  • TLDR;
  • Table of Contents
  • What are Architectural Decision Records?
  • Why we adopted ADRs
  • Why create another ADR tool?
  • Getting Started
    • Installing dotnet adr
    • Using dotnet adr
    • Configure the default ADR location in your repo
  • ADR Templates and ADR Template Packages
    • Example ADRs
    • Which ADR templates are available out of the box?
      • Alexandrian Pattern
      • Business Case Pattern
      • Markdown Architectural Decision Records (MADR)
      • Merson Pattern
      • Nygard Pattern
      • Planguage Pattern
      • Tyree and Akerman Pattern
    • Custom ADR Templates and ADR Template Packages
    • Create your own custom ADR Template Package
      • Store template file locally
  • Local System Details
  • DevOps
  • Packages
  • Community Contributions
  • Licenses
  • Project Sponsor
  • Acknowledgements
  • Code of conduct
  • IP Maturity Model (IMM)
  • IP Maturity Model Scores

What are Architectural Decision Records?

Context drives intent, which manifests as code. This is the socio-technical contract of modern software development. If over time, code is the only remaining archeological artefact, we are simply left with effect without knowing the cause.

Over the last decade we have found immense value in Gherkin based Executable Specifications to describe the behaviour (or intent) of a system; in fact the Gherkin (Specflow) feature files have often outlived the original code and have been used to re-implement the system using a more modern language or framework.

Now we have the code, and the intent, but we're still missing an artefact that captures the context. Architectural Decision Records (ADRs) fill this requirement exceedingly well. ADRs are simple text documents (our preferred format is Markdown) which précis some or all of the following aspects of a decision:

• Context
• Assumptions
• Options
• Rationale
• Decision
• Consequences

The 1st Law of Simplicity is "Reduce", and much like Bezos' infamous 6-page memo format, brevity is the key to the power of ADRs. Rather than a heavyweight functional specification, ADRs have much more in common with minutes from a meeting. The meeting may take hours, but reading the minutes, should take... minutes.

Good code comments don't explain what the code does, they explain what the developer was thinking when they wrote the code, what assumptions they were making, and what they were trying to achieve. This allows anyone reviewing the code to spot any faults with logic, assumptions that proved to be incorrect, or requirements which have evolved. ADRs operate on the same principle. Anyone can review the ADRs and quickly grok the context, the assumptions, the rationale, the decision, and the consequences, without being bogged down in detail.

With modern cloud native solutions, recording context takes on a nuanced significance; cloud services vary from IaaS to PaaS to SaaS, as a consumer you are not in control of the feature set, the scale characteristics, or the price point. When making an architectural decision you may be constrained by a missing feature, a financial budget, or a performance target. The speed of cloud innovation means that any of these constraints can change on a monthly basis. Keeping track of feature announcements and re-evaluating the context of previously made decisions is an engineering practice you should adopt as part of the ADR process.

The principles of ADRs are straightforward, but the implementation can be simple or as complex as your team or organization requires. The out-of-the-box default template is the Nygard Pattern, but this tool and repo contains a number of alternative templates you can choose from, or you can create your own. If you want to read some real ADRs, check out these examples from our own OSS projects.

We find ADRs to be most effective when they are co-located with the code, in the same repo. We've worked on projects where "all documentation lives in Wiki / Confluence / SharePoint" because not all stakeholders have access to source control repos, but we find this approach to be high friction for all parties involved. This tool, adr, is designed to encapsulate our recommended practices.

Why we adopted ADRs

Several years ago we worked on a very complex project which required R&D, technical spikes, benchmarking, load-testing, performance tuning cycles, and further benchmarking in order to find the optimal solution. This process worked incredibly well and we delivered orders of magnitude performance improvements over the existing solution.

During the end-of-project retrospective we identified two sub-optimal outcomes; firstly we felt that while we had worked minor miracles in our technical solutions, the customer never seemed particularly impressed by the improvements. Secondly, the customer hired a new architect just as we finished delivering the solution, and as part of their onboarding process reviewed the solution and criticized almost every aspect with "I wouldn't have done it that way. At my last job we approached it like X and found it to be best".

We realized that the two issues were related. For the first problem, we concluded that we had failed to follow the most basic instruction you're given at school; "show your workings". We had hidden all the hard work, all the complexity, all of the hypothesis-testing experiments, and just presented the results Fait Accompli. The second problem had the same root cause. Because we had not recorded all of our experiments in a systematic way, we had no evidence to show that the approach the architect considered "best" was actually the first approach we took, but when we benchmarked and load-tested the approach it couldn't handle the data throughput at the price-point required by the customer. "Best" is entirely based on situational context. What's "best" in one situation is inappropriate in another.

We embrace evidence-based-decision-making as part of our experimental approach, and wanted to find a process that would allow us to document this in a formalized way. We did some research and discovered Architectural Decision Records. They have now become a fundamental part of our software and data engineering processes.

As a fully-remote organization, a secondary benefit from adopting ADRs has been how it allows us to enable distributed and asynchronous evidence gathering, discussions, decision making, and onboarding. This benefit manifests in a number of different ways; firstly, the process of drafting and evolving an ADR as a working group. Secondly, once the ADR reaches its "proposed status" it's very easy for senior decision makers to quickly grok the summary of the decision and provide input. Thirdly, any new contributor can get up to speed by using the collection of ADRs, AKA an Architecture Decision Log (ADL), to understand all the historical decisions that have been made, and most importantly what the situational context was at the point the decisions were made.

Why create another ADR tool?

One of the reasons for "re-inventing the wheel" with adr when there are so many ADR tools already in existence, is that almost all of those existing tools are opinionated to the point of embedding the ADR templates into the tooling.

Since we adopted ADRs in 2018, we've changed our default template a number of times. Thus, with adr we wanted to decouple the tool from the templates, and make use of NuGet content packages as a mechanism to enable the ecosystem to build / use / share their own templates internally (using Azure DevOps or GitHub private package feeds), or publicly using nuget.org.

Getting Started

Installing dotnet adr

adr is a .NET global tool, which means once installed, it's available on the PATH of your machine.

To install the adr global tool use the following command:

dotnet tool install -g adr

To install a specific version, use:

dotnet tool install -g adr --version <version-number>

To update to the latest version of the tool, use:

dotnet tool update -g adr

To uninstall the tool, use:

dotnet tool uninstall -g adr

To list all the global tools installed on your machine, open a command prompt and type:

dotnet tool list -g

Using dotnet adr

Here is a detailed list of the available adr commands:

adr new <TITLE> - Creates a new Architectural Decision Record, from the current default ADR Template, from the current ADR Template package.

adr new <TITLE> -i <RECORD NUMBER> - Creates a new Architectural Decision Record, superseding the specified ADR record, which will have its status updated to reflect to point to this newly created ADR.

adr new <TITLE> -p <PATH> - Creates a new Architectural Decision Record, from the current default ADR Template, from the current ADR Template package, for the Architecture Knowledge Management (AKM) folder located at the specified path.

adr new <TITLE> -i <RECORD NUMBER> -p <PATH> - Creates a new Architectural Decision Record, for the Architecture Knowledge Management (AKM) folder located at the specified path, superseding the specified ADR record, which will have its status updated to reflect to point to this newly created ADR.

adr templates - Manipulate ADR Templates & ADR Template Packages. Root command for template operations. Will list available sub-commands.

adr templates show - Displays the detailed metadata of the current default ADR Template.

adr templates show --id-only - Displays the id of the current default ADR Template.

adr templates set <TEMPLATE ID> - Sets the default ADR Template. The <TEMPLATE ID> can be obtained from adr templates show

adr templates list - Displays a table containing the detailed metadata of all ADR Templates contained in the current default ADR Template Package.

adr templates list --ids-only - Displays the ids of all ADR Templates contained in the current default ADR Template Package.

adr templates list --format-list - Displays a list of the detailed metadata of all ADR Templates contained in the current default ADR Template Package.

adr templates package install - Installs the latest version of the currently set ADR Templates Package.

adr templates package update - Updates to the latest version of the currently set ADR Templates Package.

adr templates package set <PACKAGE ID> - Sets the default NuGet ADR Template Package. Use adr.templates.

adr templates package show - Displays the default NuGet ADR Template Package.

adr environment - Manipulate the dotnet-adr environment. Root command for environment operations. Will list available sub-commands.

adr environment init <PATH> - Initializes a new Architecture Knowledge Management (AKM) folder. If <PATH> is omitted, it will create docs\adr in the current directory.

adr environment reset - Resets the adr environment back to its default settings.

Configure the default ADR location in your repo

While adr is quite flexible in allowing you to specify were to create or update an ADR, either in the current directory, or by specifying a custom path using adr new <TITLE> -p <PATH>, sometime it's better to create a "pit of quality" and standardize the Architecture Knowledge Management (AKM) folder location for all users of the tool.

To support this requirement you can create a file in the root of your repo called adr.config.json which must have the following format:

{
    "path": "./Docs/Adr"
}

Where the value of path is relative to the root of the repo.

ADR Templates and ADR Template Packages

Example ADRs

It's always hard to write a document starting from scratch; this is why the default ADR templates contain guidance in the form of headings and notes. Real-world examples are always much more helpful, so below is a list of some publicly available ADRs from our Open Source projects. If you explore the repos, you can find more examples:

• Updating Rx.NET Build for .NET 7.0 era Tooling
• Implementation of client-side Claims Evaluation
• Corvus.Tenancy will not create storage containers automatically
• Multitargeting .NET Standard 2.0 and 2.1
• Integration of an Event Store for audit and "change feed" purposes

Which ADR templates are available out of the box?

We have collected a number of popular ADR templates.

NOTE: the status of the Open Source License for some of the templates is unclear. See each template for more details.

Alexandrian Pattern

ADR using the Alexandrian Pattern Language Approach coined by Architect Christopher Alexander et. al in 1977, which distils the decision record into the following headings:

• Prologue (Summary)
• Discussion (Context)
• Solution (Decision)
• Consequences (Results)

Source Joel Parker Henderson, see this issue about licensing.

Set as the default template using adr templates set alexandrian

Business Case Pattern

Emphasizes creating a business case for a decision, including criteria, candidates, and costs, created by Joel Parker Henderson, which distils the decision record into the following headings:

• Title
• Status
• Evaluation criteria
• Candidates to consider
• Research and analysis of each candidate
  • Does/doesn't meet criteria and why
  • Cost analysis
  • SWOT analysis
  • Opinions and feedback
• Recommendation

Source Joel Parker Henderson, see this issue about licensing.

Set as the default template using adr templates set business-case

Markdown Architectural Decision Records (MADR)

Architectural Decisions using Markdown and Architectural Decision Records, by Oliver Kopp, which distils the decision record into the following headings:

• Title
• Status
• Context and Problem Statement
• Decision Drivers
• Considered Options
• Decision Outcome
  • Positive Consequences
  • Negative Consequences
• Pros and Cons of the Options
  • [option 1]
  • [option 2]
  • [option 3]
• Links

Available as dual-license under MIT and CC0. You can choose between one of them if you use this work.

Set as the default template using adr templates set madr

Merson Pattern

An adaptation of the Nygard pattern, by Paulo Merson which adds the rationale behind the decision. It distils the decision record into the following headings:

• Title
• Status
• Decision
• Rationale
• Consequences

Available under the MIT License.

Set as the default template using adr templates set merson

Nygard Pattern

A simple, low-friction "Agile" ADR approach by Michael Nygard, which distils the decision record into the following headings:

• Title
• Status
• Context
• Decision
• Consequences

Available under CC0 1.0 Universal (CC0 1.0) Public Domain Dedication.

Set as the default template using adr templates set nygard

Planguage Pattern

A Quality Assurance oriented approach by John Terzakis, which distils the decision record into the following headings:

• Title
• Status
• Tag
• Gist
• Requirement
• Rationale
• Priority
• Stakeholders
• Owner
• Author
• Revision
• Date
• Assumptions
• Risks
• Defined

Source Joel Parker Henderson, see this issue about licensing.

Set as the default template using adr templates set planguage

Tyree and Akerman Pattern

ADR approach by Jeff Tyree and Art Akerman, Capital One Financial, which distils the decision record into the following headings:

• Title
• Status
• Issue
• Decision
• Group
• Assumptions
• Constraints
• Positions
• Argument
• Implications
• Related decisions
• Related requirements
• Related artifacts
• Related principles
• Notes

Source Joel Parker Henderson, see this issue about licensing.

Set as the default template using adr templates set tyree-ackerman

Custom ADR Templates and ADR Template Packages

ADR Templates are simply markdown files which contain headings and guidance for the end users. The only hard requirement is that they contains # Title and ## Status headings as adr uses Regular Expressions to find and replace these values to power the adr new <TITLE> and adr new -s <RECORD NUMBER> <TITLE> commands.

The default ADR Templates are contained in the Endjin.Adr.Templates project, which contains NuGet configuration elements in Endjin.Adr.Templates.csproj to create a NuGet "content" package, which is available via nuget.org as adr.templates.

Create your own custom ADR Template Package

While we use MADR as the default template, because it has a nice balance of simplicity and power, it doesn't mean that it's the best template for you, your team, and your organization. First check-out the different templates which are available out of the box. If none of these are suitable then it's easy to make your own!

This repo contains an example extensibility "Third Party" ADR template example located in /Solutions/ThirdParty.Adr.Templates, this is also available via nuget.org as thirdparty.adr.templates.

There are straightforward conventions for creating a customer ADR template package:

1. Create a folder which matches the name of the template, using kebab-case. i.e. my-custom-adr-template
2. Inside that folder create a template.md file
3. Add the following front-matter and mandatory headings to template.md:

---
Title: 
Description: 
Authors: 
Effort: 
More Info: 
Version: 
Last Modified: YYYY-MM-DD HH:MM
---
# Title 

## Status

4. Create a .csproj file which contains the following properties:

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <AssemblyName>thirdparty.adr.templates</AssemblyName>
    <TargetFramework>net8.0</TargetFramework>
    <IncludeBuildOutput>false</IncludeBuildOutput>
    <SuppressDependenciesWhenPacking>true</SuppressDependenciesWhenPacking>
    <!-- https://learn.microsoft.com/en-us/dotnet/core/tutorials/creating-app-with-plugin-support -->
    <EnableDynamicLoading>true</EnableDynamicLoading>
  </PropertyGroup>

  <PropertyGroup>
    <PackageLicenseExpression>Apache-2.0</PackageLicenseExpression>
    <PackageDescription>An example demonstrating how a 3rd Party could create a dotnet-adr template package.</PackageDescription>
    <PackageTags>dotnet-adr dotnet-adr-template architecture tools endjin</PackageTags>
    <PackageReleaseNotes></PackageReleaseNotes>
  </PropertyGroup>

  <ItemGroup>
    <Content Include="my-custom-adr-template\template.md">
      <PackagePath>content\my-custom-adr-template</PackagePath>
      <Pack>true</Pack>
    </Content>
  </ItemGroup>

</Project>

5. When the solution is built, a thirdparty.adr.templates.nupkg NuGet package will be created. Publish this to nuget.org

To swap between the packages use the following adr commands:

adr templates package set thirdparty.adr.templates

Next, to download the latest version of 'thirdparty.adr.templates` use the command:

adr templates install

To see the currently set default package, use:

adr templates package show

To see the id of the currently set default template, use:

adr templates show

To revert to the "official" ADT Template Package you can either, reset the environment:

adr environment reset

or:

adr templates package set adr.templates

Then:

adr templates install

Store template file locally

Optionally, store the template file file inside the repository, and specify the TemplatePath in the adr.config.json file.

{
    "templatePath": "./Docs/adr-template.md"
}

Local System Details

adr stores various configuration files and packages in an application profile folder created in:

%%UserProfile%%\AppData\Roaming\endjin\dotnet-adr

Templates are stored in:

templates\

Configuration in:

configuration\

The templates NuGet package is cached in %%UserProfile%%\.nuget\packages.

DevOps

The project is hosted on GitHub and uses a GitHub Actions workflow and Endjin.RecommendedPractices.Build to manage the full DevOps lifecycle.

Packages

The NuGet packages for the project, hosted on NuGet.org are:

• adr
• adr.templates
• thirdparty.adr.templates

If you want to Create your own custom ADR Template Package, please add dotnet-adr to the PackageTags element.

Community Contributions

• 2023-07-19 - James Broome provides an overview of ADRs and some examples.
• 2023-06-23 - Rodrigo Juarez provides an overview of ADRs for .NET Developers and shows you how to get started with adr: What Are Architecture Design Records (ADR), and How Can You Get Started as a .NET Developer?
• 2021-08-09 - Christopher Laine wrote a nice blog post about ADRs and dotnet adr: Architectural Decision Records (ADR) with dotnet-adr

Licenses

This project is available under the Apache 2.0 open source license.

For any licensing questions, please email [email protected]

Project Sponsor

This project is sponsored by endjin, a UK based Technology Consultancy which specializes in Data, AI, DevOps & Cloud, and is a .NET Foundation Corporate Sponsor.

We help small teams achieve big things.

We produce two free weekly newsletters:

• Azure Weekly for all things about the Microsoft Azure Platform
• Power BI Weekly for all things Power BI, Microsoft Fabric, and Azure Synapse Analytics

Keep up with everything that's going on at endjin via our blog, follow us on Twitter, YouTube or LinkedIn.

We have become the maintainers of a number of popular .NET Open Source Projects:

• Reactive Extensions for .NET
• Reaqtor
• Argotic Syndication Framework

And we have over 50 Open Source projects of our own, spread across the following GitHub Orgs:

• endjin
• Corvus
• Menes
• Marain
• AIS.NET

And the DevOps tooling we have created for managing all these projects is available on the PowerShell Gallery.

For more information about our products and services, or for commercial support of this project, please contact us.

Acknowledgements

• Patrik Svensson for his help, support, feature requests, and amazing work on Spectre.Console, and Covenant
• Joel Parker Henderson for collating the various ADR templates we make use of.
• David Glick for his incredibly useful blog series on the NuGet v3 SDK API.
• Martin Björkström for his excellent gist that does the heavy lifting of downloading and extracting NuGet packages.

Code of conduct

This project has adopted a code of conduct adapted from the Contributor Covenant to clarify expected behaviour in our community. This code of conduct has been adopted by many other projects. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

IP Maturity Model (IMM)

The IP Maturity Model is endjin's IP quality assessment framework, which we've developed over a number of years when doing due diligence assessments of 3rd party systems. We've codified the approach into a configurable set of rules, which are committed into the root of a repo, and a Azure Function HttpTrigger HTTP endpoint which can evaluate the ruleset, and render an svg badge for display in repo's readme.md.

IP Maturity Model Scores

dotnet-adr's Issues

Nuget badge on github page

It would be handy to have a nuget badge in the main readme.md (including preview versions) to make it obvious what the latest version is when installing.

Thought you might like to know

I love your dotnet-adr tool so much, I added an article about it to my engineering blog.

https://medium.com/it-dead-inside/architectural-decision-records-adr-with-dotnet-adr-9fa76104bcd7?source=friends_link&sk=7549ae2a650eeaa188b7318726a2eab9

Cheers

Chris Laine

Supersede using the MADR template

Trying to supersede a decision when using the MADR template doesn't appear to update the original decision status.

example:
adr templates set madr
adr new decision1
adr new decision2 -i 1

decision2 gets created, and the output from adr indicates "Superseded ADR record; 1" but 0001-decision1.md is not updated with the superseded status.

I think the status in the template isn't matching the regex used to search for the status in NewAdrCommand.cs, If Status is a level 2 heading ( ## Status) then the supersede works correctly.

Init information issue

Your getting started section mention the use of adr init as one way to initialize an environment on the current folder, but that command will return a No such command error message. Instead I needed to use adr environment init

I'm getting an "Object reference not set to an instance of an object." when I try to use adr new

On a clean computer, trying to run the commands like in the TLDR section will return the error when I try to use adr new "test"

Please let me know if you need any additional information

Consider abstractions for filesystem actions

I'm writing some tests for a new feature (#222) and understandably for a tool like this there's a lot of use of filesystem operations like Environment.CurrentDirectory. I'd like to replace these with abstractions (probably System.IO.Abstractions for actual filesystem related stuff) and will go ahead with that unless someone replies here telling me I'm wasting my time and that PR will never be considered. :)

dotnet tool install -g fails with no package found

When following the instructions for the installation of dotnet-adr,, the readme states just run
dotnet tool install -g adr

However, doing so bombs with the following error

error NU1103: Unable to find a stable package adr with version (>= 0.0.0)
error NU1103: - Found 4 version(s) in nuget.org [ Nearest version: 0.1.0-preview.36 ]
The tool package could not be restored.

This appears to be because there is no 1.0.0+ version of the nuget package.

Looking at the build status on the repo, this package is not being actively built / deployed to nuget. Happy to help to get this going if you need contributors.

Cheers

New command to set status for an ADR

Can't set template default

I'm trying to change the default template to nygard (https://github.com/endjin/dotnet-adr#nygard-pattern) with the following error

Use docs\adr folder automatically for all commands, not just init

If you run this command from the root folder of your repo:

adr init

it will add a new subfolder, docs\adr, which is the standard place for ADR records to live. If you then run the following command without changing the current directory:

adr new "Tabs vs spaces"

This will not add the new entry in docs\adr. Instead it will put it in the folder you're currently in.

Unless there's some good reason not to, we should consider making the various commands consistently presume that docs\adr is the place for ADR records by default.

We might want to consider whether it's worth being clever enough to walk up the folder heirarchy (stopping at the folder containing the .git subfolder) to locate the docs\adr folder automatically even if you're in a subfolder at the time.

Build.ps1 fails downloading PowerShell package

1. Forked repo
2. Executed build.ps1

Expected
Build to run

Actual
Build failed with following error:

Install-PSResource: C:\Code\Github\dotnet-adr\build.ps1:90
Line |
  90 |      Install-Module InvokeBuild -RequiredVersion $InvokeBuildModuleVer …
     |      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Unable to successfully install package 'InvokeBuild': 'Object reference not set to an instance of an object.' to
     | temporary installation path.

Additional context

13:39:39 C:\Code\Github\dotnet-adr PS> get-psresourceRepository

Name      Uri                                      Trusted Priority
----      ---                                      ------- --------
PSGallery https://www.powershellgallery.com/api/v2 False   50

Implemented a simplified gitops way to manage ADRs

Hello

New user of this very useful tool.
Were there discussions to facilitate collaboration through gitops ?

I see this could be useful:

• Creation of a markdown page summarizing all of the ADRs grouped by status
• Enable creation of ADRs across different folders with a folder representing a lifecycle status or a "domain"
• Facilitate the above by implementing an index for the ADR repository which would you hold things like policies and unique identifiers
• Generation of relative links when cross referencing ADRs

Linux compatibility?

Hey there,

Thanks for this great tool - I've been using it for a while with the pre-release version inside a linux-based vscode devcontainer, but recently upgraded to 1.1.6 and now I get the following error for almost all adr commands:

Error: The parameter pathString is not an absolute directory path because it doesn't have a drive letter syntax (like "C:\") nor a URN path syntax (like "\\server\share\"). (Parameter 'pathString')

I've taken a look through the source and it seems this error is coming from the forked NDepend.Path dependency, but it's not 100% clear what code path is getting to the error, or which path needs fixing.

My suspicion was that it's the use of System.Environment.SpecialFolder.ApplicationData as an input to the NDepend.Path's ToAbsoluteDirectoryPath - so I've tried setting XDG_CONFIG_HOME explicitly as this is the env var used on linux to define that special folder. (It defaults to $HOME/.config) But it doesn't affect the outcome either way.

Looking at the source of NDepend.Path, it's not clear to me if it actually supports linux-style paths? All the test cases are for windows or UNC style paths, and indeed there is a test case that seems to explicitly suggest it doesn't support them, because it asserts that / is not a valid absolute path, but on linux of course it is the valid absolute root path.

Any thoughts? Would love to be able to use the updated version, otherwise I'll have to abandon this project because of a chain of dependency conflicts in my devcontainer (the prerelease version depends on dotnet 3.1, which depends on libssl1.1 which is not available in the debian/ubuntu versions that are avilable for .net 7.0).

Thanks!

Consider ditching SpecFlow and using regular nunit style tests

I'm just working on adding support for a command to set the default path for ADR files, and most of my time has been spent wrangling SpecFlow. I could have written a single nunit test and just got on with things, but TDD is a real pain with so much boilerplate.

It's your game, so it's your rules, but I gotta tell ya, I wouldn't be upset if I could submit a PR to simplify it by removing SpecFlow entirely from the solution... :)

New command to set the default path in an adr.config.json

Clarify terminology for "repository"

Hello, me again. I'm just wondering, before I make a mistake, what this project means when the word "repository" is used?

Is it expected to mean:

1. The git repository that the ADRs are being stored in (i.e. the folder containing the .git folder)?
2. The folder containing the ADRs (bearing in mind it's possible to provide a path to almost anywhere within the working copy when creating new ADRs)?

My confusion comes from https://github.com/endjin/dotnet-adr/blob/main/Solutions/Endjin.Adr.Cli.Specs/Features/Init.feature, which I think makes it sound like "an ADR repository within a source code repository". But then, with that said, I don't see anywhere that actually creates a readme.md, so I can't tell if that is meant to go in the root of the git repo, or in the docs/adr folder?