Skip to content

Auto-generate RSS Feed content

Brian Rhea requested to merge auto-gen-breaking-changes-rss into master

Why is this change being made?

In order to ensure the Breaking Changes RSS feed remains up-to-date, this creates a task to auto-generate the feed.

A follow-up step will be to add this to the pipeline schedule after it is merged.

Related to: Product#4714 (closed)

This MR:

  • Creates bin/generate-breaking-changes-rss to trigger ReleasePosts::BreakingChangesRSS.new.create
  • Creates lib/release_posts/breaking_changes_rss.rb to fetch release post deprecation MRs from gitlab-org/gitlab, read the contents of the changes, and amend /breaking-changes.xml
  • Creates lib/release_posts/merge_request.rb to create MR objects after fetched
  • Adds bin/generate-breaking-changes-rss to the pipeline

Author Checklist

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

Edited by Brian Rhea

Merge request reports