Skip to content

Only run CI on pushes to master and on all pull requests #1670

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

Merged
merged 1 commit into from
Jan 9, 2022

Conversation

filmor
Copy link
Member

@filmor filmor commented Jan 9, 2022

Fixes #1668

What does this implement/fix? Explain your changes.

...

Does this close any currently open issues?

...

Any other comments?

...

Checklist

Check all those that are applicable and complete.

  • Make sure to include one or more tests for your change
  • If an enhancement PR, please create docs and at best an example
  • Add yourself to AUTHORS
  • Updated the CHANGELOG

@lostmsu
Copy link
Member

lostmsu commented Jan 9, 2022

Maybe add release branches too? Might need to name them in a certain way, like release/2.5

@filmor
Copy link
Member Author

filmor commented Jan 9, 2022

We don't really have release branches so far (only backporting for 2.5 for a while), though we could start that with 3.0.

@filmor filmor merged commit 75f4398 into pythonnet:master Jan 9, 2022
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.

Duplicate CI runs when using branches directly in pythonnet repo.
2 participants