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

[fix/calens-master-commit] Calens GitHub action: Master Commit #1391

Merged
merged 2 commits into from
Sep 24, 2024

Conversation

hosy
Copy link
Collaborator

@hosy hosy commented Sep 23, 2024

Description

Change the GitHub Action to commit changes directly to the master branch.

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (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 change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • Added an issue with details about all relevant changes in the iOS documentation repository.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • Added changelog files for the fixed issues in folder changelog/unreleased

@hosy hosy marked this pull request as ready for review September 23, 2024 13:48
Copy link
Member

@DeepDiver1975 DeepDiver1975 left a comment

Choose a reason for hiding this comment

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

Technically this looks good. No idea if this is necessary on each and every push.
Not up to be to decide.

@hosy hosy merged commit 46a7b59 into master Sep 24, 2024
3 checks passed
@DeepDiver1975 DeepDiver1975 deleted the fix/calens-master-commit branch September 24, 2024 09:49
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.

3 participants