b5a168aa0e
doc: Streamline remote handling in releasing docs ( #9603 )
...
The docs already assume an 'upstream' remote, so we can only fetch from there instead of fetching all remotes. We also don't need to hardcode the remote URL.
2022-02-04 12:13:33 +01:00
49278c1df8
RELEASING: should also tag dev0 for prereleases
2021-12-07 15:04:27 +02:00
c19f63d39d
Adjust releasing infra/docs ( #8795 )
...
* Adjust releasing infra/docs
Follow-up for #8150 , see #7507
* Add suggestions
2021-06-28 12:24:48 +02:00
5ae2106059
fix a command in RELEASING.rst
2021-05-04 09:25:11 -07:00
ff6d5ae278
port the rest of the scripts/docs over to the main branch
2021-03-18 22:13:12 +01:00
f6b682ad49
RELEASING: start new dev cycle by tagging MAJOR.{MINOR+1}.0.dev0 in master
...
This is needed so setuptools-scm in master shows an accurate version.
In particular, higher than the stable branch.
2020-11-13 12:38:58 +02:00
027415502a
RELEASING: clarify where to push the tag
2020-09-19 21:35:17 +03:00
d7ad55bb2a
Add docs for releasing major/release candidates
...
Fix #7447
2020-08-01 13:51:12 -03:00
22acbaf393
Minor changes to the release process
...
As discussed in https://github.com/pytest-dev/pytest/pull/7556
2020-07-29 11:35:27 -03:00
38029828d1
Support generating major releases using issue comments ( #7548 )
2020-07-28 13:40:14 +02:00
15e1dd0f87
Automate release by comment notifications ( #6823 )
...
* Automate release by comment notifications
* Only run if @pytestbot is mentioned
2020-03-01 14:46:35 -03:00
c3e53a072d
Switch to new git workflow
...
Co-Authored-By: Daniel Hahler <git@thequod.de>
2020-02-12 09:49:21 +02:00
Florian Bruhin
Ran Benita
Anthony Sottile
Ronny Pfannschmidt
Bruno Oliveira