Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Remove duplicate "master" from the branches list | Christopher Baines | 2025-02-11 |
| | |||
* | Use the data service for the list of branches | Christopher Baines | 2025-02-06 |
| | | | | | | | As it's custom configuration to limit the branches is causing issues here, patches are being applied on top of a branch when the data serivce doesn't have data for that branch, causing it to be re-created over and over again. | ||
* | Update Guile Knots | Christopher Baines | 2025-01-14 |
| | |||
* | Fix listing branches with open merge issues | Christopher Baines | 2025-01-13 |
| | |||
* | Avoid repeatedly recreating issue branches if the branch doesn't exist | Christopher Baines | 2025-01-12 |
| | | | | At least in the data service. | ||
* | Use more from knots | Christopher Baines | 2025-01-06 |
| | |||
* | Don't keep requesting the latest processed master branch revision | Christopher Baines | 2024-06-12 |
| | |||
* | Log the base commit hash used | Christopher Baines | 2024-06-12 |
| | |||
* | Pre-compute the branch, and use the issue title as well | Christopher Baines | 2024-05-15 |
| | | | | | This allows changing the branch that QA applies the patches to by changing the title of the issue. | ||
* | Sort the patches before applying them to the git branch. | Vivien Kraus | 2024-04-16 |
| | | | | | | | | | | | | | | | | | By default, the patches are not ordered. Because of the unreliability of e-mail delivery, they can be received completely out of order. Patchwork may also re-order them, and they may get ordered by commit author date (or, equivalently, e-mail Date header). Both possibilities lead to failure to apply patches if the order is incorrect for two patches that do not commute. The patch name contains a header: [bug#xxx,v12,i/n] where "i" is the variable part and indicates the patch number. Git pads "i" with zeros if needed. The string order of the names is thus the true commit order. * guix-qa-frontpage/manage-patch-branches.scm (create-branch-for-issue): Sort patches according to their "name". | ||
* | Fix checking for unknown commits | Christopher Baines | 2024-04-02 |
| | |||
* | Fix ordering of simple-format call | Christopher Baines | 2024-04-02 |
| | |||
* | Add more logging around checking base branch changes | Christopher Baines | 2024-04-02 |
| | |||
* | Enable checking for base revision changes for all branches | Christopher Baines | 2024-04-02 |
| | |||
* | Fix not deleting some patch branches | Christopher Baines | 2024-04-01 |
| | | | | When the patches were for a non-master branch. | ||
* | Add a buffer to prevent deleting some branches that aren't found | Christopher Baines | 2024-03-17 |
| | | | | To reduce instances of branches getting repeatedly deleted then recreated. | ||
* | Avoid timeouts blocking creating issue branches | Christopher Baines | 2023-10-27 |
| | |||
* | Delete the create branch for issue logs | Christopher Baines | 2023-10-27 |
| | | | | | When looking at creating the branch, to ensure the log inserted (if any) is fresh. | ||
* | Fix checking for changes against master | Christopher Baines | 2023-10-22 |
| | |||
* | Handle the case when a series has no patches | Christopher Baines | 2023-10-21 |
| | | | | In patchwork-series->branch. | ||
* | Highlight the intended branch on the issue page | Christopher Baines | 2023-10-21 |
| | |||
* | Start applying patches to non-master branches | Christopher Baines | 2023-10-21 |
| | | | | If this is indicated when the patch is submitted. | ||
* | Check if all patches have been received earlier | Christopher Baines | 2023-10-21 |
| | |||
* | Add parse-patch-name | Vivien Kraus | 2023-10-21 |
| | | | | | | | This is a cut down version of the original patch. Using this information will require some refactoring first. Signed-off-by: Christopher Baines <mail@cbaines.net> | ||
* | Fix calling create-branch-for-issue | Christopher Baines | 2023-10-19 |
| | |||
* | Log more when patches haven't been received | Christopher Baines | 2023-10-18 |
| | |||
* | Rework managing patch branches | Christopher Baines | 2023-10-18 |
| | | | | | Delete branches which no longer appear in the latest patchwork series and simplify some of the code. | ||
* | Refactor fetching data from patchwork | Christopher Baines | 2023-10-17 |
| | | | | | | | | | Fetch pages one at a time until the required number of patch series has been fetched. This commit also changes the ordering from issue number to the series ID, which will mean that series associated with older issues will be prefered over newer issues with older series. | ||
* | Improve cache clearing when recreating issue branches | Christopher Baines | 2023-10-16 |
| | |||
* | Fix an issue with applying patches | Christopher Baines | 2023-10-13 |
| | | | | The base commit hash was being fetched before it had been created. | ||
* | Instrument manage patch branches | Christopher Baines | 2023-10-06 |
| | |||
* | Use --ignore-whitespace when applying patches | Christopher Baines | 2023-09-30 |
| | |||
* | Better handle patches that don't apply | Christopher Baines | 2023-09-19 |
| | |||
* | Rework applying patches | Christopher Baines | 2023-09-19 |
| | | | | To capture the output from git am. | ||
* | Add missing #:unwind? #t | Christopher Baines | 2023-09-15 |
| | |||
* | Ignore exceptions when deleting the base-for-issue- tag | Christopher Baines | 2023-08-29 |
| | | | | As it might have already been deleted. | ||
* | Switch to using i686-linux for checking whether to rebase issues | Christopher Baines | 2023-08-01 |
| | | | | | As this will detect cases where the base or target revision is missing most i686-linux and armhf-linux derivations. | ||
* | Set thread names | Christopher Baines | 2023-07-25 |
| | | | | To help with debugging. | ||
* | Add a new package changes page | Christopher Baines | 2023-07-05 |
| | | | | And make some refactoring to make this easier. | ||
* | Try to reduce the frequency of the requests to issues.guix.gnu.org | Christopher Baines | 2023-05-31 |
| | | | | To avoid the DoS protection. | ||
* | Memoize checking for changes against the latest master revision | Christopher Baines | 2023-05-23 |
| | | | | To speed this up. | ||
* | Delete patch branches where master has changed too much | Christopher Baines | 2023-05-23 |
| | | | | | | Since the patches were applied. This will help clear out patch branches after big changes (e.g. core-updates) so that the patch branches can be regenerated against an up to date master branch commit. | ||
* | Improve checking for patch branches to delete | Christopher Baines | 2023-03-03 |
| | | | | | Lock the repository for shorter periods, and only when necessary. Plus improve exception handling and logging. | ||
* | Tweak and join up how many patch series are processed | Christopher Baines | 2023-02-17 |
| | | | | By different parts of the code. | ||
* | Increase the number of series to create branches for | Christopher Baines | 2023-02-14 |
| | |||
* | Further tweak managing patch branches | Christopher Baines | 2023-02-14 |
| | |||
* | Fix deleting patch branches | Christopher Baines | 2023-02-14 |
| | | | | | | Previously this wasn't working as getting the refs for the comparison was broken, this approach with just checking the revision details should be faster though. | ||
* | Fix some variable issues | Christopher Baines | 2022-12-09 |
| | |||
* | Make sure to delete branches when applying patches fails | Christopher Baines | 2022-12-09 |
| | | | | | As it's important not to leave a branch around that doesn't correspond to the latest set of patches. | ||
* | Guard against missing patchwork series dates | Christopher Baines | 2022-12-09 |
| |