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

Create first PR to avoid direct push #296

Conversation

masesdevelopers
Copy link
Contributor

Description

This PR is needed to check the first execution of the new build.yaml

Related Issue

#295

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.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@masesdevelopers masesdevelopers added documentation Improvements or additions to documentation enhancement New feature or request github_actions Pull requests that update GitHub Actions code labels Oct 29, 2023
@masesdevelopers masesdevelopers self-assigned this Oct 29, 2023
@masesdevelopers masesdevelopers merged commit 4cc602a into masesgroup:master Oct 30, 2023
5 checks passed
@masesdevelopers masesdevelopers deleted the 295-avoid-direct-push-of-documentation-use-pr-instead branch October 30, 2023 00:37
@masesdevelopers masesdevelopers linked an issue Oct 30, 2023 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request github_actions Pull requests that update GitHub Actions code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Avoid direct push of documentation, use PR instead
1 participant