cube-doctor issueshttps://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/issues2022-04-12T09:17:21Zhttps://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/issues/59Update default message for MR from cube-doctor2022-04-12T09:17:21ZNoé GaumontUpdate default message for MR from cube-doctorHi,
Context: https://forge.extranet.logilab.fr/cubicweb/cubes/jsonb/-/merge_requests/30
The current message is :
> Hello dear contributors,
> This is an auto generated modification to help you improve the code base of logilab. If ...Hi,
Context: https://forge.extranet.logilab.fr/cubicweb/cubes/jsonb/-/merge_requests/30
The current message is :
> Hello dear contributors,
> This is an auto generated modification to help you improve the code base of logilab. If this commit is bad don't hesitate to close this MR and report it here https://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/issues.
> Kind regards,
It would be great to have a link to the project with the refactor.
In fact, this MR induces a new lower bound for cubicweb and this should be included in the MRhttps://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/issues/58Improve copyright year update regular expression2022-01-05T09:44:36ZSimon ChabotImprove copyright year update regular expressionSome copyright year are different from the one that is currently handled by cube-doctor.
see for instance here: https://forge.extranet.logilab.fr/cubicweb/cubes/rememberme/-/merge_requests/26/diffs
where we have:
```
:copyright: 2009-2...Some copyright year are different from the one that is currently handled by cube-doctor.
see for instance here: https://forge.extranet.logilab.fr/cubicweb/cubes/rememberme/-/merge_requests/26/diffs
where we have:
```
:copyright: 2009-2011
```
We should update the regular expression, or test against different copyright format.https://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/issues/57Use cache of cloned repos instead of cloning them multiple times2021-10-20T21:04:46ZArthur LutzUse cache of cloned repos instead of cloning them multiple times![Screenshot_from_2021-10-15_17-26-48](/uploads/ac26f04ed18e9fc689443887cc7298ac/Screenshot_from_2021-10-15_17-26-48.png)
In the above example, extracted from https://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/jobs/419718/ , it se...![Screenshot_from_2021-10-15_17-26-48](/uploads/ac26f04ed18e9fc689443887cc7298ac/Screenshot_from_2021-10-15_17-26-48.png)
In the above example, extracted from https://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/jobs/419718/ , it seems that addressbook cube is cloned 9 times in different /tmp folders.
Could there be an optimisation where the first clone is in /tmp/abcd, then the other clones do so from /tmp/abcd instead of from heptapod ?https://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/issues/56Slow down the rate of the `hg clone ` commands2021-10-28T01:53:08ZArthur LutzSlow down the rate of the `hg clone ` commandsauto-mr is a heavy user of `hg clone` and thus asks a lot of ressources at a rather fast rate.
Maybe adding a little rate limiting would be nice.auto-mr is a heavy user of `hg clone` and thus asks a lot of ressources at a rather fast rate.
Maybe adding a little rate limiting would be nice.https://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/issues/55rule "npm update"2021-09-01T09:49:14ZNicolas Chauvatnicolas.chauvat@logilab.frrule "npm update"add a rule that does "npm update" and creates a merge request if the resulting package-lock.json is different.add a rule that does "npm update" and creates a merge request if the resulting package-lock.json is different.https://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/issues/54remove pyramid from cubicweb extras up of 3.32.02021-08-26T09:32:38ZArthur Lutzremove pyramid from cubicweb extras up of 3.32.0From what I understand, upwards of 3.32.0 cubicweb has pyramid by default so I would imagine we don't need extra=pyramid anymore.
cube-doctor created a patch with `cubicweb[pyramid,crypto]": ">=3.33.0,<3.34.0",` is that a bug ?
Could...From what I understand, upwards of 3.32.0 cubicweb has pyramid by default so I would imagine we don't need extra=pyramid anymore.
cube-doctor created a patch with `cubicweb[pyramid,crypto]": ">=3.33.0,<3.34.0",` is that a bug ?
Could cube-doctor go through projects and remove the `[pyramid]` for projects that are upwards of 3.32.0 ?https://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/issues/53create docker image and use it in scheduled jobs2021-10-28T01:53:25ZNicolas Chauvatnicolas.chauvat@logilab.frcreate docker image and use it in scheduled jobslet the CI build the docker image and store it in heptapod's registry, then use it in the scheduled jobs to save the build timelet the CI build the docker image and store it in heptapod's registry, then use it in the scheduled jobs to save the build timehttps://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/issues/52add release-new2021-08-05T08:24:32ZLaurent Peuchadd release-newNoé GaumontNoé Gaumonthttps://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/issues/51add a script to replace docker cubicweb images by the new cubicweb-base image2021-08-05T08:24:58ZLaurent Peuchadd a script to replace docker cubicweb images by the new cubicweb-base imageSimon ChabotSimon Chabothttps://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/issues/50.cube-doctor.yml2021-11-05T15:37:24ZLaurent Peuch.cube-doctor.ymlCurrent identified things needs to be done to finish and put `.cube-doctor.yml` in production (this is not the whole picture yet):
- [X] in auto-mr code, take into account the merge_when_pipeline_succeeds defined in `.cube-doctor.yml`
-...Current identified things needs to be done to finish and put `.cube-doctor.yml` in production (this is not the whole picture yet):
- [X] in auto-mr code, take into account the merge_when_pipeline_succeeds defined in `.cube-doctor.yml`
- [x] in add-new-rules, add code to add a new rule for set-cubicweb-max-version
- [ ] should we add a new option to specific if cube-doctor should or shouldn't rebase its MR?
- [ ] for now there is not configuration format validation
- [ ] we've talked about making cube-doctor open bugs in that situation
- [ ] add set-cubicweb-max-version in the README.rst (both in `.cube-doctor.yml` example and in its own section), maybe do the same with `rebase-all-my-mrs`
- [x] faire un mécanisme de béta pour commencer à l'utiliser sur des cubes progressivementLaurent PeuchLaurent Peuchhttps://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/issues/49cube-doctor can update his own MR2021-09-23T19:49:52ZLaurent Peuchcube-doctor can update his own MRLaurent PeuchLaurent Peuchhttps://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/issues/48extend cube-doctor to code-doctor2021-08-04T16:02:37ZNicolas Chauvatnicolas.chauvat@logilab.frextend cube-doctor to code-doctorrename it once it is not limited to cubes anymore.rename it once it is not limited to cubes anymore.https://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/issues/47cube-doctor to rebase his merge requests2021-08-04T16:12:32ZArthur Lutzcube-doctor to rebase his merge requestsIn some cases, the initial merge request generated by cube-doctor is created when the .gitlab-ci.yml in the project doesn't enable one to easily integrate the proposed code changes.
It would be nice to have a manual or automated action...In some cases, the initial merge request generated by cube-doctor is created when the .gitlab-ci.yml in the project doesn't enable one to easily integrate the proposed code changes.
It would be nice to have a manual or automated action that rebases the created MRs to the new public head.https://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/issues/46task to remove a tox section2021-07-22T14:53:19ZArthur Lutztask to remove a tox sectionOn some cubes, there are some unused tox sections, where would one start to create a task to remove a section from the ini file that configures tox ?
Example with `[testenv:flake8-jenkins]` : https://forge.extranet.logilab.fr/cubicweb...On some cubes, there are some unused tox sections, where would one start to create a task to remove a section from the ini file that configures tox ?
Example with `[testenv:flake8-jenkins]` : https://forge.extranet.logilab.fr/cubicweb/cubes/blog/-/merge_requests/24/diffs
Thanks!https://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/issues/45deb-publish or not deb-publish ? that is the question !2021-08-04T16:12:29ZNicolas Chauvatnicolas.chauvat@logilab.frdeb-publish or not deb-publish ? that is the question !when cube-doctor removed the `debian/` directory and the `deb-publish` section from `tox.ini`, it should not add it back the day after !
see for example:
- remove debian/ and deb-publish https://forge.extranet.logilab.fr/cubicweb/cubes...when cube-doctor removed the `debian/` directory and the `deb-publish` section from `tox.ini`, it should not add it back the day after !
see for example:
- remove debian/ and deb-publish https://forge.extranet.logilab.fr/cubicweb/cubes/addressbook/-/merge_requests/18
- add deb-publish back to tox.ini https://forge.extranet.logilab.fr/cubicweb/cubes/addressbook/-/merge_requests/20 qui le remet
a solution could be to test for the presence of debian/ before adding deb-publish to tox.inihttps://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/issues/44integrate prettier for js/ts and maybe other (css? sass?)2021-06-11T12:24:56ZLaurent Peuchintegrate prettier for js/ts and maybe other (css? sass?)https://prettier.io/https://prettier.io/https://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/issues/43integrate pyupgrade2021-08-04T15:59:15ZNicolas Chauvatnicolas.chauvat@logilab.frintegrate pyupgradesee https://github.com/asottile/pyupgradesee https://github.com/asottile/pyupgradehttps://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/issues/42explore flakehell2021-05-05T22:33:45ZLaurent Peuchexplore flakehellIt might be worth it https://github.com/flakehell/flakehellIt might be worth it https://github.com/flakehell/flakehellhttps://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/issues/41[dependabot] Copy commits / pull requests made by dependabot on github2021-04-15T09:21:19ZArthur Lutz[dependabot] Copy commits / pull requests made by dependabot on githubIn the case of a client project which has open sourced the code, the code is mirrored on github and so we got some merge requests from dependabot https://github.com/culturecommunication/francearchives-cubicweb-edition/pulls
It would be...In the case of a client project which has open sourced the code, the code is mirrored on github and so we got some merge requests from dependabot https://github.com/culturecommunication/francearchives-cubicweb-edition/pulls
It would be nice for cube-doctor to copy those commits and submit them to the project (where the CI can give an indication of the impact).https://forge.extranet.logilab.fr/cubicweb/cube-doctor/-/issues/40[proposed upgrades] find a way to flag and remind maintainers to take care of MR2021-04-15T09:15:23ZArthur Lutz[proposed upgrades] find a way to flag and remind maintainers to take care of MRWhen a MR for proposed upgrades (requirements.txt or package.json) has it's tests green it should be easy for maintainers to merge it. For red dependency upgrades that fail it could result in a "we'll handle that one later, we're focusin...When a MR for proposed upgrades (requirements.txt or package.json) has it's tests green it should be easy for maintainers to merge it. For red dependency upgrades that fail it could result in a "we'll handle that one later, we're focusing on features" and for theses red MRs to be forgotten or become stock.
Maybe we could have a different reminder message, for example "make sure you have an issue created explaining why this MR is not managed (for now). And that this issue is visible to the team and maybe the client too".