Allow for manual runs of SF CLI Integration Test#104
Conversation
|
|
||
| on: | ||
| pull_request: | ||
| workflow_dispatch: |
There was a problem hiding this comment.
This allows us to run this github action on main, manually in the github UI.
There was a problem hiding this comment.
"Us" being any user with write access to the repo.
| enable = true | ||
| pattern = "^v(?P<base>.+)$" | ||
| format-jinja = "{% if distance == 0 %}{{ base }}{{ stage or '' }}{% else %}{{ bump_version(base) }}.dev{{ distance }}+{{ commit }}{% endif %}" | ||
| pattern = "^v(?P<base>\\d+\\.\\d+\\.\\d+)(?P<stage>\\.dev\\d+|a\\d+|b\\d+|rc\\d+)?$" |
There was a problem hiding this comment.
The problem we're solving here is when installing/running locally, if the base branch was .dev1, then .post... would be appended to it and that wouldn't match pep440. This makes it so, if you're already working on a tag (like locally), it just uses that instead of trying to add anything.
| ``` | ||
|
|
||
| 4. **Initialize a project for development work verification** | ||
| 4. **Install the SF CLI and plugin** |
There was a problem hiding this comment.
I realize this is getting ahead of the README itself, but I started adding the poetry build instructions (below) as a side effect and realized this really needs to be our main development path- not a side note.
|
|
||
| on: | ||
| pull_request: | ||
| workflow_dispatch: |
There was a problem hiding this comment.
"Us" being any user with write access to the repo.
2 participants
No description provided.