aboutsummaryrefslogtreecommitdiff
path: root/guix-qa-frontpage/view
Commit message (Collapse)AuthorAge
* Fix the package changes table on the branch pageChristopher Baines2023-11-03
| | | | And only display the "below systems" message if there are any.
* Use a different symbol when waiting for build resultsChristopher Baines2023-11-03
| | | | | And group these issues towards the top of the patches list since they potentially can be merged if there's not too many builds remaining.
* Start to better describe when builds are waiting to happenChristopher Baines2023-11-02
| | | | | Don't use the same styling as failed builds on the issue page, and also separate out the systems which don't count towards the issue status.
* Link to the /reproducible-builds pageChristopher Baines2023-11-01
|
* Make the branches table shorterChristopher Baines2023-11-01
|
* Add a Guix logo to the headerChristopher Baines2023-11-01
|
* Add a simple package pageChristopher Baines2023-10-31
|
* Add a reproducible-builds page to display data and issuesChristopher Baines2023-10-30
| | | | Maybe this will be a useful starting point.
* Sort and filter the branch package reproducibility tableChristopher Baines2023-10-30
| | | | Removing systems for which substitutes aren't available.
* Fetch and display package reproducibility information for branchesChristopher Baines2023-10-29
| | | | This involved some refactoring of branch data in general.
* Make "large-number-of-builds" an issue statusChristopher Baines2023-10-29
| | | | Rather than these falling within the unknown status.
* Support filtering by branchChristopher Baines2023-10-21
|
* Highlight the intended branch on the issue pageChristopher Baines2023-10-21
|
* Add a new patches missing statusChristopher Baines2023-10-18
|
* Refactor fetching data from patchworkChristopher Baines2023-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.
* Show the changes to cross derivations on issue pagesChristopher Baines2023-10-15
|
* Show the merged with issuesChristopher Baines2023-10-13
|
* Only show the create branch log if it's availableChristopher Baines2023-10-10
|
* Remove peekChristopher Baines2023-10-10
|
* Improve error reporting around branchesChristopher Baines2023-10-10
|
* Allow filtering issues by statusChristopher Baines2023-10-02
|
* Link and show some patches stats on the homepageChristopher Baines2023-09-30
|
* Add some more issue statusesChristopher Baines2023-09-27
| | | | So it's easier to find issues that have specific problems.
* Add a mechanism to add the reviewed-looks-good usertag to issuesChristopher Baines2023-09-26
| | | | | As a way of trying to prioritise merging patches that have been reviewed by someone.
* Make reviewed-looks-good an issue statusChristopher Baines2023-09-26
|
* Show the guix usertags on the issue pageChristopher Baines2023-09-26
|
* Better handle patches that don't applyChristopher Baines2023-09-19
|
* Pull some divs out of the issue viewChristopher Baines2023-09-19
| | | | To make it easier to read.
* Fix uri encoding of derivation filenamesChristopher Baines2023-09-16
|
* Fix some links to derivationsChristopher Baines2023-09-15
|
* Display the README as a pageChristopher Baines2023-09-04
| | | | Like the data service.
* Make sure to include more builds on the package changes pagesChristopher Baines2023-07-21
| | | | | As previously builds that went from an unknown or blocked status wouldn't appear.
* Fix "View comparison" links on the issue pagesChristopher Baines2023-07-21
|
* Provide more information on the selected optionsChristopher Baines2023-07-21
| | | | On the package changes pages.
* Improve the styling of the package changes pageChristopher Baines2023-07-21
|
* Port the package changes functionality from branches to issuesChristopher Baines2023-07-21
|
* Add a new package changes pageChristopher Baines2023-07-05
| | | | And make some refactoring to make this easier.
* Improve display of too many changes for branchesChristopher Baines2023-07-03
|
* Style the branch packages information red when it's unavailableChristopher Baines2023-06-17
|
* Add some links to the branch pagesChristopher Baines2023-06-17
|
* Fix displaying error information on the branch pageChristopher Baines2023-06-17
|
* Handle the cached exceptions in the issue viewChristopher Baines2023-06-17
|
* Improve error reporting on the issue pageChristopher Baines2023-06-16
| | | | | | This regressed when more data started to be cached, since the exceptions couldn't be stored in the db, but now some of the information makes it through.
* Tweak the home pageChristopher Baines2023-06-15
| | | | | Move the contributing information to the bottom, and move the patches link above branches.
* Use the right to/tooChristopher Baines2023-06-09
| | | | Thanks Andreas.
* Make branch builds conditional on master branch substitute availabilityChristopher Baines2023-06-03
| | | | | As is done for patches. While the build coordinator prioritises the builds, I think this can stil help make best use of the build farm.
* Improve messaging around low substitute availabilityChristopher Baines2023-06-03
|
* Highlight when branches are out of dateChristopher Baines2023-06-02
|
* Highlight low master branch substitute availability on the issue pageChristopher Baines2023-06-02
|
* Show a table of branches on the homepageChristopher Baines2023-05-24
|
generated by cgit v1.2.3 (git 2.49.0) at 2025-05-09 10:56:50 +0000