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: CHANGELOG.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,14 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
6
and this project adheres to [PEP 440](https://www.python.org/dev/peps/pep-0440/)
7
7
and uses [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
8
8
9
+
10
+
## [0.5.0]
11
+
### Added
12
+
- Added a CLI option to specify the name of a user GitHub Token in the rendered plugin for the GitHub Actions workflows that require it.
13
+
- A GitHub Actions workflow that will ensure hyp3-cookiecutter renders.
14
+
### Fixed
15
+
- Fixed project name variable error which prevented the cookiecutter from rendering.
16
+
9
17
## [0.4.0]
10
18
### Changed
11
19
- In the generated project, ruff and mypy dependencies are now statically pinned and kept up to date with dependabot to prevent updates introducing unexpected static analysis failures
Copy file name to clipboardExpand all lines: README.md
+32-15Lines changed: 32 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,24 +7,43 @@ generate a new HyP3 Plugin.
7
7
8
8
### 1. Create the plugin with Cookiecutter
9
9
10
-
To create a new plugin, you'll first need to run the cookicutter.
11
-
From a terminal on your local development machine, navigate to where you'd like
12
-
to create the local copy of the plugin's repository. Then run cookiecutter and
13
-
follow the prompts:
10
+
To create a new plugin, you'll first need to run [`cookiecutter`](https://cookiecutter.readthedocs.io/en/stable/), which you can install with [`conda`/`mamba`](https://docs.conda.io/projects/conda/en/latest/user-guide/install/index.html)
Now, you should have a `hyp3-<process>` directory which contains a minimal HyP3
21
-
plugin.
39
+
> [!TIP]
40
+
> The `github_*` prompts facilitate the CI/CD pipelines included in the cookiecutter. These can be for yourself, or a shared team "bot" user, and we'll set up a Personal Access Token in [Section 6](#6-create-a-personal-access-key-for-github-actions).
41
+
42
+
Now, you should have a `hyp3-<process_type>` (`hyp3-foo-bar` in the example above) directory which contains a minimal HyP3 plugin.
22
43
23
44
### 2. Create a repository on GitHub
24
45
25
46
Next, we'll need to create a new repository on [GitHub](https://github.com) for your plugin.
26
-
Make sure to create your repository in the same user/organization account you set in the
27
-
`<GITHUB_USERNAME>` field of the cookiecutter.
28
47
29
48
Your repository name should be the same as the directory name for the plugin you created
30
49
on your local develop machine. (e.g., `hyp3-<PROCESS_TYPE>`). For the description section,
@@ -136,16 +155,16 @@ article
136
155
### 6. Create a personal access key for GitHub Actions
137
156
138
157
Some of the GitHub actions (`release.yml` and `tag-version.yml`) need extra permissions to work
139
-
properly. These actions will attempt to use the `GITHUB_PAK` secret to assume a user profile
140
-
with the needed permissions, so we'll need to create the permissions/secret.
158
+
properly and will attempt to assume those permission via a repository secret named `<github_actions_token>`.
159
+
So, if it doesn't already exist, we will need to create the token.
141
160
142
161
1. In your user/organization settings:
143
162
* Click on Developer Settings
144
163
* Click on Personal access tokens
145
164
* Click Tokens (classic)
146
165
* Click Generate new token
147
166
* Click Generate new token (classic)
148
-
* In the note section give the token a name (e.g., `GITHUB_PAK`)
167
+
* In the note section give the token a name (e.g., `<GH_ACCOUNT_NAME>_PAK`)
149
168
* Check the boxes for:
150
169
* repo
151
170
* workflow
@@ -158,7 +177,7 @@ with the needed permissions, so we'll need to create the permissions/secret.
158
177
* Click on Secrets and variables
159
178
* Click on Actions
160
179
* Click on New repository Secret
161
-
* Name your secret `GITHUB_PAK`
180
+
* Name your secret `<GH_ACCOUNT_NAME>_PAK`
162
181
* Paste in the access token you save from the last step
0 commit comments