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.

Sign up for GitHub

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

Jump to bottom

Update workflows with POM generation #129

Merged
merged 2 commits into from
Feb 9, 2023
Merged

Update workflows with POM generation #129

merged 2 commits into from
Feb 9, 2023

Conversation

masesdevelopers
Copy link
Contributor

@masesdevelopers masesdevelopers commented Feb 9, 2023 •
edited
Loading

Description

The PR updates the workflows following the same command-line used in KNet. This avoids issue during workflow execution.

Related Issue

Closed #128

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 the bug Something isn't working label Feb 9, 2023
@masesdevelopers masesdevelopers self-assigned this Feb 9, 2023
@masesdevelopers masesdevelopers merged commit 107e711 into masesgroup:master Feb 9, 2023
@masesdevelopers masesdevelopers deleted the 128-use-changes-within-workflows-to-solve-issue-in-jnet branch February 9, 2023 22:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@masesdevelopers masesdevelopers

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Use changes within workflows to solve issue in JNet
1 participant
@masesdevelopers