Commit e7d4728
committed
fix(deploy): commit changes to current branch instead
Committing the changes to another branch and switching back means the
newly added keys are not present in the .sops.yaml file in the branch
that we are working in.
There isn't really a need to push the changes to another branch or the
remote. I'd rather commit changes into the host branch I'm currently
working on so as to keep these changes together in their own PR.1 parent 1455d45 commit e7d4728
1 file changed
+0
-7
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | 3 | | |
4 | | - | |
5 | 4 | | |
6 | 5 | | |
7 | | - | |
8 | | - | |
9 | | - | |
10 | 6 | | |
11 | | - | |
12 | 7 | | |
13 | 8 | | |
14 | 9 | | |
15 | 10 | | |
16 | 11 | | |
17 | | - | |
18 | 12 | | |
19 | | - | |
20 | 13 | | |
21 | 14 | | |
0 commit comments