Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use CHANGELOG in top level repo #186

Merged
merged 3 commits into from
Feb 7, 2020
Merged

Conversation

TheAngryByrd
Copy link
Owner

Proposed Changes

Closes #185.

Types of changes

What types of changes does your code introduce to MiniScaffold?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • Build and tests pass locally
  • I have added tests that prove my fix is effective or that my feature works (if appropriate)
  • I have added necessary documentation (if appropriate)

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

Jimmy Byrd added 3 commits February 7, 2020 10:00
Removes RELEASE_NOTES and uses CHANGELOG generated from helper script in tools with some minor manual fixes
@TheAngryByrd TheAngryByrd force-pushed the 185-toplevel-changelog branch from ad045d9 to 03cb861 Compare February 7, 2020 16:13
@TheAngryByrd TheAngryByrd merged commit f821453 into master Feb 7, 2020
@TheAngryByrd TheAngryByrd deleted the 185-toplevel-changelog branch February 7, 2020 17:03
TheAngryByrd pushed a commit that referenced this pull request Feb 7, 2020
## [0.23.0-beta001] - 2020-02-07

### Changed
- Templates now use [KeepAChangelog](https://keepachangelog.com/) instead of [RELEASE_NOTES](https://fake.build/apidocs/v5/fake-core-releasenotes.html) from [@rmunn](https://github.com/rmunn) - (#175)
- Main project now use [KeepAChangelog](https://keepachangelog.com/) instead of [RELEASE_NOTES](https://fake.build/apidocs/v5/fake-core-releasenotes.html) from [@TheAngryByrd](https://github.com/TheAngryByrd) - (#186)
TheAngryByrd pushed a commit that referenced this pull request Feb 13, 2020
## [0.23.0] - 2020-02-13

### Changed
- Templates now use [KeepAChangelog](https://keepachangelog.com/) instead of [RELEASE_NOTES](https://fake.build/apidocs/v5/fake-core-releasenotes.html) from [@rmunn](https://github.com/rmunn) - (#175)
- Main project now use [KeepAChangelog](https://keepachangelog.com/) instead of [RELEASE_NOTES](https://fake.build/apidocs/v5/fake-core-releasenotes.html) from [@TheAngryByrd](https://github.com/TheAngryByrd) - (#186)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Convert top level build script to use CHANGELOG in #175
1 participant