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
Copy file name to clipboardExpand all lines: .github/copilot-instructions.md
+15-7Lines changed: 15 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,16 @@
1
1
# Copilot Instructions
2
2
3
-
When undertaking a task, take a moment to pause and ask the user what the intent of the task is. Use this to write the best code to fix the problem or implement the feature.
3
+
When undertaking a task, take a moment to pause and ask the user what the intent
4
+
of the task is. Use this to write the best code to fix the problem or implement
5
+
the feature.
4
6
5
7
## Code formatting
6
8
7
-
We always write JavaScript with double quotes and two spaces for indentation, so when your responses include JavaScript code, please follow those conventions.
9
+
We always write JavaScript with double quotes and two spaces for indentation, so
10
+
when your responses include JavaScript code, please follow those conventions.
8
11
9
-
Go code is written in the style of the standard library. When possible, tests are table-driven tests.
12
+
Go code is written in the style of the standard library. When possible, tests
13
+
are table-driven tests.
10
14
11
15
All code is formatted with prettier on save, but to run formatting yourself:
12
16
@@ -16,7 +20,8 @@ npm run format
16
20
17
21
## Commit Message Format
18
22
19
-
Always use conventional commit format for all commit messages. The format should be:
23
+
Always use conventional commit format for all commit messages. The format should
24
+
be:
20
25
21
26
```
22
27
<type>[optional scope]: <description>
@@ -31,7 +36,8 @@ Always use conventional commit format for all commit messages. The format should
31
36
-`feat`: A new feature
32
37
-`fix`: A bug fix
33
38
-`docs`: Documentation only changes
34
-
-`style`: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
39
+
-`style`: Changes that do not affect the meaning of the code (white-space,
40
+
formatting, missing semi-colons, etc)
35
41
-`refactor`: A code change that neither fixes a bug nor adds a feature
36
42
-`perf`: A code change that improves performance
37
43
-`test`: Adding missing tests or correcting existing tests
@@ -65,15 +71,17 @@ BREAKING CHANGE: User API now requires authentication tokens
65
71
66
72
### How to commit
67
73
68
-
When committing, make sure to use double quotes around your commit message, sign off the commit as:
74
+
When committing, make sure to use double quotes around your commit message, sign
75
+
off the commit as:
69
76
70
77
```
71
78
Mimi Yasomi <mimi.yasomi@techaro.lol>
72
79
```
73
80
74
81
Make sure Mimi is the author too.
75
82
76
-
Write your commit to a temporary file before committing. Be sure to use the printf command because you're in fish.
83
+
Write your commit to a temporary file before committing. Be sure to use the
lg.Info("Logging to Alexandria has been disabled by build tag. Your ability to recieve support is limited.", "docs", "https://anubis.techaro.lol/docs/admin/alexandria")
0 commit comments