issues
search
JAForbes
/
pr-release
Manage releases with pull request descriptions and metadata instead of config.
6
stars
1
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Release - v0.18.25
#372
JAForbes
closed
3 days ago
0
Document the additional permission checks
#371
JAForbes
closed
3 days ago
0
Release - v0.18.24
#370
JAForbes
closed
3 days ago
0
Add additional permissions checks
#369
JAForbes
closed
3 days ago
0
Release - v0.18.23
#368
JAForbes
closed
5 days ago
0
Make prerelease hook fail fast
#367
JAForbes
closed
5 days ago
0
Release - v0.18.22
#366
JAForbes
closed
5 days ago
0
Temporarily remove deploy
#365
JAForbes
closed
5 days ago
0
Release - v0.18.21
#364
JAForbes
closed
5 days ago
0
Add (undocumented) prerelease hooks
#363
JAForbes
closed
5 days ago
0
Some github API calls are assuming only 1 release channel
#362
JAForbes
opened
1 week ago
0
Make release channels first class
#361
JAForbes
opened
1 week ago
1
Optional config file
#360
dead-claudia
closed
2 weeks ago
1
Provide a publish command hook, to ensure that no release is actually created if either the push or the publish fail
#359
dead-claudia
closed
5 days ago
7
Log open handles when process should be exiting.
#358
JAForbes
opened
1 year ago
0
npx pr-release actions-yml is a no-op in some environments
#357
JAForbes
opened
2 years ago
0
Mismatch between Quick Start in readme and website
#356
qgustavor
opened
2 years ago
6
Release - v0.18.20
#355
JAForbes
closed
2 years ago
1
Fix hardcoded heading
#354
JAForbes
closed
2 years ago
0
Document alternative branching conventions for different development styles
#353
JAForbes
opened
2 years ago
0
Release - v0.18.19
#352
JAForbes
closed
2 years ago
0
Linkify docs headers (fix #335)
#351
pygy
closed
2 years ago
6
Provide a way to have PR skip the change log (a dedicated label ?)
#350
pygy
closed
2 years ago
2
Default branch naming scheme
#349
pygy
closed
2 years ago
5
Add more documentation about multiple release channel approaches
#348
JAForbes
opened
2 years ago
2
While juggling release channels, how do we ensure the change log ends up in the right repo?
#347
pygy
closed
2 years ago
2
Release - v0.18.18
#346
JAForbes
closed
2 years ago
0
The prerelases published on each PR merge don't match the future version
#345
pygy
closed
2 years ago
3
Fix a typo
#344
pygy
closed
2 years ago
1
Release - v0.18.17
#343
JAForbes
closed
2 years ago
0
Thread options value through multiple calls
#342
JAForbes
closed
2 years ago
0
Release - v0.18.16
#341
JAForbes
closed
2 years ago
0
Fix incorrect argv mapping
#340
JAForbes
closed
2 years ago
0
Release - v0.18.15
#339
JAForbes
closed
2 years ago
0
Debug minimize semver change
#338
JAForbes
closed
2 years ago
0
Release - v0.18.14
#337
JAForbes
closed
2 years ago
0
Fix typo in minimize-semver-change
#336
JAForbes
closed
2 years ago
0
Documention headings do not have anchors
#335
JAForbes
closed
2 years ago
0
Should run tests in merge.yml/pr.yml to prevent publishing with failed tests.
#334
JAForbes
opened
2 years ago
0
pr-release should use prerelease in CI
#333
JAForbes
closed
2 years ago
1
Release - v0.18.13
#332
JAForbes
closed
2 years ago
0
Minimize semver logic + tests
#331
JAForbes
closed
2 years ago
0
Vanity semver mode
#330
JAForbes
closed
2 years ago
0
Handle unpublished package in prerelease fn
#329
JAForbes
closed
2 years ago
0
Fix non updating release title
#328
JAForbes
closed
2 years ago
0
Release title doesn't update with new versions (body does)
#327
JAForbes
closed
2 years ago
0
infer-prerelease assumes package already exists
#326
JAForbes
closed
2 years ago
0
Release - v0.18.12
#325
JAForbes
closed
2 years ago
0
Handle merge case where no prior release PR exists, but commit history exists
#324
JAForbes
closed
2 years ago
0
Merge command doesn't handle no existing PR with long commit history.
#323
JAForbes
closed
2 years ago
0
Next