Skip to content

Conversation

@tim-vk
Copy link
Contributor

@tim-vk tim-vk commented Nov 28, 2022

Since my previous PR created linter errors on master & release_*:
Both linter & unittests now run on pull requests.
Unittests only run on changed .py file.
Linter always runs

Maintainers will complete the following section

  • Commit messages are descriptive enough
  • Code coverage from testing does not decrease and new code is covered

@tim-vk tim-vk force-pushed the feature/linter_on_PR branch from 9f0f678 to 11a990c Compare November 28, 2022 21:56
@tim-vk tim-vk changed the title Feature/linter on pr Run the linter on a pull request. Nov 28, 2022
@tim-vk tim-vk changed the title Run the linter on a pull request. Run the linter and unit tests on a pull request. Nov 28, 2022
@rcerven
Copy link
Member

rcerven commented Nov 29, 2022

how is this different from what we already have? CIs are already running when you create PR, reason why some steps didn't run for your previous PR is unknown but I'd say there was something up with the actions

@tim-vk
Copy link
Contributor Author

tim-vk commented Nov 29, 2022

Hmm... odd

I figured this would be the issue since my other PR also has actions that didn't run (here). But When checking other (older) pr's it seems you are right. Apolagies!

@tim-vk tim-vk closed this Nov 29, 2022
@rcerven
Copy link
Member

rcerven commented Nov 29, 2022

I've just tried test PR #138, and it runs all actions without problem ....

but your PR #129 has conflicts so I think you have to resolve those first

@tim-vk
Copy link
Contributor Author

tim-vk commented Nov 29, 2022

I saw! Awsome that you double checked it. I closed this PR.

Given the discussion in PR #129 I think I'll make a new branch (& PR) and close that one.

@rcerven
Copy link
Member

rcerven commented Nov 29, 2022

you can just reuse branch & pr you have, for sake of conversation in that PR

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.

2 participants