mitre-attack / mitre-attack/attack-workbench-frontend

Release Notes Composer

Open
#85 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

collections enhancement
Dominant language
TypeScript
Stars
438
Forks
79
Avg merge
1d 21h
Merged PRs (30d)
3

Description

As a data provider, I want to be able to easily compose release notes when I publish a new release of a collection.

Release notes are a part of the collection index, which is not generated as part of this application. However, when a user creates a new release of a collection (#5) we should provide auto-generated release notes (akin to #74) so that the user can easily populate their index release notes with a list of changes in the new version.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the release-creation flow described in issue #5 and the auto-generated notes precedent in issue #74. Determine how a new collection release can expose its changes for composing index release notes; the work is done when creating a release provides usable release notes for the publisher.

Written by the indexing model from the issue text.

Assessment

Tech stack
angular, typescript
Domain
frontend, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.