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

DTL-5457 Install CI/CD for app-extensions-sdk #42

Merged
merged 3 commits into from
Oct 10, 2024

Conversation

maximlishchenko
Copy link
Contributor

uses: pipedrive-actions/github-actions-workflows/.github/workflows/reusable_cicd-npm-publish.yml@master
with:
revision: ${{ github.event.pull_request.head.ref }}
supported_versions: '[18]'
Copy link

Choose a reason for hiding this comment

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

Remove this, lets keep with the default we have in the .nvmrc

CHANGELOG.md Outdated
@@ -7,6 +7,10 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.

## [Unreleased]

### Changed
- Migrate publish flow from Jenkins to GitHub Actions
- Fix Owner name
Copy link

Choose a reason for hiding this comment

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

Which owner name we are fixing?

@maximlishchenko maximlishchenko marked this pull request as ready for review October 8, 2024 13:47
@maximlishchenko maximlishchenko requested a review from a team as a code owner October 8, 2024 13:47
@maximlishchenko maximlishchenko added npm-version-patch used for deployment npm-ready-for-publish used for deployment and removed npm-ready-for-publish used for deployment labels Oct 8, 2024
CHANGELOG.md Outdated
Comment on lines 11 to 12
- Migrate publish flow from Jenkins to GitHub Actions
- Add devops-tooling as owner for .github/workflows/cicd_*
Copy link
Member

Choose a reason for hiding this comment

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

Is it necessary to include these details in public changelog?

If there even is a need to release a new version, I would keep this information more vague. If it can just be merged to master, then I would exclude adding changelog at all 🤔

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I updated the readme to be more vague. The patch label is needed to test that the release process is working.

@maximlishchenko maximlishchenko added the npm-ready-for-publish used for deployment label Oct 10, 2024
pipedrive-public-gha-bot bot pushed a commit that referenced this pull request Oct 10, 2024
@maximlishchenko maximlishchenko added npm-ready-for-publish used for deployment and removed npm-ready-for-publish used for deployment labels Oct 10, 2024
pipedrive-public-gha-bot bot pushed a commit that referenced this pull request Oct 10, 2024
@pipedrive-public-gha-bot pipedrive-public-gha-bot bot merged commit 225bb26 into master Oct 10, 2024
12 of 13 checks passed
@pipedrive-public-gha-bot pipedrive-public-gha-bot bot deleted the install-cicd-app-extensions-sdk branch October 10, 2024 13:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
npm-ready-for-publish used for deployment npm-version-patch used for deployment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants