You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- name: Check for Change File(s) in .autover/changes/
22
+
run: |
23
+
DIRECTORY=".autover/changes/"
24
+
if echo "${{ steps.changed-files.outputs.all_changed_files }}" | grep -q "$DIRECTORY"; then
25
+
echo "✅ One or more change files in '$DIRECTORY' are included in this PR."
26
+
else
27
+
echo "❌ No change files in '$DIRECTORY' are included in this PR."
28
+
echo "Refer to the 'Adding a change file to your contribution branch' section of https://github.com/aws/integrations-on-dotnet-aspire-for-aws/blob/main/CONTRIBUTING.md"
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+45Lines changed: 45 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -40,6 +40,51 @@ GitHub provides additional document on [forking a repository](https://help.githu
40
40
[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
41
41
42
42
43
+
## Adding a `change file` to your contribution branch
44
+
45
+
Each contribution branch should include a `change file` that contains a changelog message for each project that has been updated, as well as the type of increment to perform for those changes when versioning the project.
46
+
47
+
A `change file` looks like the following example:
48
+
```json
49
+
{
50
+
"Projects": [
51
+
{
52
+
"Name": "Aspire.Hosting.AWS",
53
+
"Type": "Patch",
54
+
"ChangelogMessages": [
55
+
"Fixed an issue causing a failure somewhere"
56
+
]
57
+
}
58
+
]
59
+
}
60
+
```
61
+
The `change file` lists all the modified projects, the changelog message for each project as well as the increment type.
62
+
63
+
These files are located in the repo at .autover/changes/
64
+
65
+
You can use the `AutoVer` tool to create the change file. You can install it using the following command:
66
+
```
67
+
dotnet tool install -g AutoVer
68
+
```
69
+
70
+
You can create the `change file` using the following command:
71
+
```
72
+
autover change --project-name "Aspire.Hosting.AWS" -m "Fixed an issue causing a failure somewhere
73
+
```
74
+
Note: Make sure to run the command from the root of the repository.
75
+
76
+
You can update the command to specify which project you are updating.
77
+
The available projects are:
78
+
* Aspire.Hosting.AWS
79
+
80
+
The possible increment types are:
81
+
* Patch
82
+
* Minor
83
+
* Major
84
+
85
+
Note: You do not need to create a new `change file` for every changelog message or project within your branch. You can create one `change file` that contains all the modified projects and the changelog messages.
86
+
87
+
43
88
## Finding contributions to work on
44
89
Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any 'help wanted' issues is a great place to start.
0 commit comments