Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: postgres/pgcommitfest
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: d17a0a8
Choose a base ref
...
head repository: postgres/pgcommitfest
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 96b0469
Choose a head ref
  • 8 commits
  • 16 files changed
  • 2 contributors

Commits on Jun 9, 2025

  1. Introduce Drafts page and automatic CF creation 

    This introduce a new type of CommitFest a "Draft" CommitFest. This
CommitFest is never "In Progress", but it can be open. It exists for a
year. It opens when the final regular CommitFest of the year becomes "In
Progress" and stays open for exactly a year. It never becomes "In
Progress" itself.

Adding a second type of CommitFest also needed a redesign of quite a few
things, like the homepage. Also management of the CommitFests needed to
be made a bit easier, so admins don't forget to close/create Draft
CommitFests. So now, closing/opening/creating CommitFests is done
automatically when the time is right for that. A help page is also
introduced to explain the CommitFest app.

The naming of CommitFests has been changed too. Since we now have a
Draft CF every year that needs a name, it seemed reasonable to align the
names of the other CFs with that too. So each PG release cycle now has 5
regular commitfests that are called:

- PG18-1
- PG18-2
- PG18-3
- PG18-4
- PG18-Final

And a single Draft CommitFest, called:

- PG18-Draft

Finally, it also adds a small initial API endpoint for the CFBot, to
request the commitfests that need CI runs. Future PRs will extend this
API surface to also include/allow requesting the actual patches that CI
should run on.

Co-Authored-By: David G. Johnston <david.g.johnston@gmail.com>
    @JelteF @polobo
    JelteF and polobo committed Jun 9, 2025
    Configuration menu
    Copy the full SHA
    90792d1 View commit details
    Browse the repository at this point in the history

  2. Don't automatically create commitfests in dev environments

    @JelteF
    JelteF committed Jun 9, 2025
    Configuration menu
    Copy the full SHA
    570b787 View commit details
    Browse the repository at this point in the history

  3. Add "Returned with Feedback" and expand explanation of other patch st… 

    …atuses
    @JelteF
    JelteF committed Jun 9, 2025
    Configuration menu
    Copy the full SHA
    975e365 View commit details
    Browse the repository at this point in the history

  4. Add commet about reasoning why we update commitfests in this kinda we… 

    …ird way
    @JelteF
    JelteF committed Jun 9, 2025
    Configuration menu
    Copy the full SHA
    4fd357f View commit details
    Browse the repository at this point in the history

  5. Missing word in help page

    @JelteF
    JelteF committed Jun 9, 2025
    Configuration menu
    Copy the full SHA
    a29aa00 View commit details
    Browse the repository at this point in the history

  6. Automatically move patches in open CF to in progress CF if they get c… 

    …ommitted
    @JelteF
    JelteF committed Jun 9, 2025
    Configuration menu
    Copy the full SHA
    4c4a2c6 View commit details
    Browse the repository at this point in the history

  7. Fix bug setting committer

    @JelteF
    JelteF committed Jun 9, 2025
    Configuration menu
    Copy the full SHA
    f6c61e7 View commit details
    Browse the repository at this point in the history

  8. Automatically move committed draft patches to the open commitfest

    @JelteF
    JelteF committed Jun 9, 2025
    Configuration menu
    Copy the full SHA
    96b0469 View commit details
    Browse the repository at this point in the history
Loading