release-new merge requestshttps://forge.extranet.logilab.fr/open-source/release-new/-/merge_requests2021-04-13T16:50:42Zhttps://forge.extranet.logilab.fr/open-source/release-new/-/merge_requests/16Topic/default/ci templates2021-04-13T16:50:42ZSimon ChabotTopic/default/ci templatesSimon ChabotSimon Chabothttps://forge.extranet.logilab.fr/open-source/release-new/-/merge_requests/15fix: replace the default rev selection to include all the ancestors of the cu...2021-03-16T17:30:23ZSimon Chabotfix: replace the default rev selection to include all the ancestors of the current commitPreviously we selected all the commit between the last tag and the current
commit, but the last tag was not necessarily an ancestor of the current commit.
Therefore a lot of commit were missing.Previously we selected all the commit between the last tag and the current
commit, but the last tag was not necessarily an ancestor of the current commit.
Therefore a lot of commit were missing.Simon ChabotSimon Chabothttps://forge.extranet.logilab.fr/open-source/release-new/-/merge_requests/14Topic/default/emojis2021-03-16T17:28:22ZSimon ChabotTopic/default/emojisFabien Amargerfabien.amarger@logilab.frFabien Amargerfabien.amarger@logilab.frhttps://forge.extranet.logilab.fr/open-source/release-new/-/merge_requests/13fix: check if we are on the latest public head /of the current branch/2021-03-05T14:27:37ZLaurent Peuchfix: check if we are on the latest public head /of the current branch/This will allow releases on different branches of CW for example (right now it only work for release on default branch)This will allow releases on different branches of CW for example (right now it only work for release on default branch)Noé GaumontNoé Gaumonthttps://forge.extranet.logilab.fr/open-source/release-new/-/merge_requests/12fix: on "hg status" ignore untracked files2021-03-05T18:16:37ZLaurent Peuchfix: on "hg status" ignore untracked filesI'm not 100% sure that we want to do that but that makes sens in my context.I'm not 100% sure that we want to do that but that makes sens in my context.Simon ChabotSimon Chabothttps://forge.extranet.logilab.fr/open-source/release-new/-/merge_requests/11feat(no-previous-tag-check): add option to not check previous tag2021-02-19T08:41:14ZNoé Gaumontfeat(no-previous-tag-check): add option to not check previous tagFabien Amargerfabien.amarger@logilab.frFabien Amargerfabien.amarger@logilab.frhttps://forge.extranet.logilab.fr/open-source/release-new/-/merge_requests/10feat(pkginfo): add a 'version' string in the pkginfo2021-02-12T17:31:11ZSimon Chabotfeat(pkginfo): add a 'version' string in the pkginfothis is need for the logigraphe.
cf this line: https://forge.extranet.logilab.fr/logilab/logigraphe/-/blob/branch/default/logigraphe/graphers/heptapod_grapher.py#L98this is need for the logigraphe.
cf this line: https://forge.extranet.logilab.fr/logilab/logigraphe/-/blob/branch/default/logigraphe/graphers/heptapod_grapher.py#L98Noé GaumontNoé Gaumonthttps://forge.extranet.logilab.fr/open-source/release-new/-/merge_requests/9doc: add a read me2021-02-12T09:24:13ZNoé Gaumontdoc: add a read mehttps://forge.extranet.logilab.fr/open-source/release-new/-/merge_requests/8fix(debian): replace Nicolas email adress by a more generic one2021-02-11T09:18:54ZSimon Chabotfix(debian): replace Nicolas email adress by a more generic oneNoé GaumontNoé Gaumonthttps://forge.extranet.logilab.fr/open-source/release-new/-/merge_requests/7feat: invite the user to publish its work if it's on the last public commit2021-02-12T08:24:47ZSimon Chabotfeat: invite the user to publish its work if it's on the last public commitElodie ThiéblinElodie Thiéblinhttps://forge.extranet.logilab.fr/open-source/release-new/-/merge_requests/6feat: add a new default option which try to guess the release type2021-02-12T08:44:46ZSimon Chabotfeat: add a new default option which try to guess the release typeBREAKING CHANGE: the default was 'patch', it is now 'auto'
if conventional commits are used, one can benefit the 'auto' mode which will
try to guess the release type based on the history.BREAKING CHANGE: the default was 'patch', it is now 'auto'
if conventional commits are used, one can benefit the 'auto' mode which will
try to guess the release type based on the history.Fabien Amargerfabien.amarger@logilab.frFabien Amargerfabien.amarger@logilab.frhttps://forge.extranet.logilab.fr/open-source/release-new/-/merge_requests/5fix: abort the command if there is some work in progress2021-02-11T12:23:38ZSimon Chabotfix: abort the command if there is some work in progressbreaking change: before that commit, the work in progress was added to the
commit creating the releasebreaking change: before that commit, the work in progress was added to the
commit creating the releasehttps://forge.extranet.logilab.fr/open-source/release-new/-/merge_requests/4Topic/default/fix ci2021-02-10T15:06:11ZNoé GaumontTopic/default/fix cihttps://forge.extranet.logilab.fr/open-source/release-new/-/merge_requests/3Topic/default/release ci2021-02-10T14:59:33ZNoé GaumontTopic/default/release cihttps://forge.extranet.logilab.fr/open-source/release-new/-/merge_requests/2fix: change web url2021-02-10T14:00:26ZNoé Gaumontfix: change web urlArthur LutzArthur Lutzhttps://forge.extranet.logilab.fr/open-source/release-new/-/merge_requests/1feat make release-new compatible with itself2021-02-09T08:27:09ZNoé Gaumontfeat make release-new compatible with itselfcloses #2closes #2Frank BessouFrank Bessou