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

v2.1.0-beta.6 -> production #43

Merged
merged 13 commits into from
May 9, 2023
Merged

v2.1.0-beta.6 -> production #43

merged 13 commits into from
May 9, 2023

Conversation

nightknighto
Copy link
Contributor

@nightknighto nightknighto commented May 9, 2023

  • release highlight feature

0-vortex and others added 13 commits April 19, 2023 11:08
* origin/main:
  chore(patch): release 2.0.1 [skip ci]
* feat: getuserdata private

* fix: fix incorrect import

* feat: refractor & add local scripts

* feat: add local dev generation script

* last touches

* refractor: suggestions

* docs: add documentation for local dev script

* refractor: change output folder

* update local dev user command name
## [2.1.0-beta.1](v2.0.1...v2.1.0-beta.1) (2023-04-26)

### 🍕 Features

* adding utilities for cards local generation & testing ([#34](#34)) ([c5a5fec](c5a5fec))
* test: add more cards

* fix: fix overflowing language bar
## [2.1.0-beta.2](v2.1.0-beta.1...v2.1.0-beta.2) (2023-04-30)

### 🐛 Bug Fixes

* Overflowing language bar fix ([#38](#38)) ([3dc1a0a](3dc1a0a))
* feat: get highlight data function

* feat: setup highlight testing

* feat: data interfaces

* refractor: split card codes

* feat: highlight cards code structure

* refractor: template shared folder

* refractor: card footer component

* refractor: separate o ut card style setup

* feat: highlights UI complete

* lint
## [2.1.0-beta.3](v2.1.0-beta.2...v2.1.0-beta.3) (2023-05-02)

### 🍕 Features

* Highlight Cards UI Generation (frontend-only) ([#36](#36)) ([138a847](138a847))
* feat: higlight card upload & storage

* feat: added parse int pipe

* parseIntPipe

* type fixes

* feat: check if highlight needs regeneration

* lint
## [2.1.0-beta.4](v2.1.0-beta.3...v2.1.0-beta.4) (2023-05-04)

### 🍕 Features

* higlight card upload & storage ([#39](#39)) ([b6abefa](b6abefa))
* feat: github pr data insertion

* requested changes

* nit: remove unneeded typing

* lint

* type refractor

* lint
## [2.1.0-beta.5](v2.1.0-beta.4...v2.1.0-beta.5) (2023-05-05)

### 🍕 Features

* highlights getting repo name & languages from pr's repo ([#41](#41)) ([1555a25](1555a25))
* feat: remove lang gaps

* feat: decrease user repos limit

* feat: use user's github login name
## [2.1.0-beta.6](v2.1.0-beta.5...v2.1.0-beta.6) (2023-05-09)

### 🍕 Features

* UI adjustments ([#42](#42)) ([acbe81a](acbe81a))
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Compliance Checks

Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.

Issue Reference

In order to be considered for merging, the pull request description must refer to a specific issue number. This is described in our Contributing Guide.
This check is looking for a phrase similar to: "Fixes #XYZ" or "Resolves #XYZ" where XYZ is the issue number that this PR is meant to address.

Protected Branch

In order to be considered for merging, the pull request changes must not be implemented on the "beta" branch. This is described in our Contributing Guide. We would suggest that you close this PR and implement your changes as described in our Contributing Guide and open a new pull request.

Conventional Commit PR Title

In order to be considered for merging, the pull request title must match the specification in conventional commits. You can edit the title in order for this check to pass.
Most often, our PR titles are something like one of these:

  • docs: correct typo in README
  • feat: implement dark mode"
  • fix: correct remove button behavior

Linting Errors

  • Found type "null", must be one of "feat","fix","docs","style","refactor","perf","test","build","ci","chore","revert"
  • No subject found

Watched Files

This pull request modifies specific files that require careful review by the maintainers.

Files Matched

  • npm-shrinkwrap.json
  • package.json

@0-vortex 0-vortex changed the title release highlight feature v2.1.0-beta.6 -> production May 9, 2023
@nightknighto nightknighto merged commit 41a34b2 into main May 9, 2023
2 of 6 checks passed
@github-actions
Copy link

github-actions bot commented May 9, 2023

🎉 This PR is included in version 2.1.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants