Skip to content

ci(enhancement): Do not trigger Github Actions for doc or Readme changes #102

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 5 commits into from
Aug 12, 2020
Merged

ci(enhancement): Do not trigger Github Actions for doc or Readme changes #102

merged 5 commits into from
Aug 12, 2020

Conversation

coder3101
Copy link
Contributor

As pointed out by @jwakely in this comment #99 (comment) it is not wise to trigger CI for changes in docs or any other non-code related changes. This commit relaxes the trigger restriction on PR and Push event so that they are only triggered when at least one file changed which does not belong to the below list:

  • Markdown changed (anything ending with .md)
  • Anything inside doc subdirectory.

@coder3101
Copy link
Contributor Author

Travis and Appveyor will still trigger. They are legacy CI we will drop in future, so let them get triggered until their removal.

@codecov
Copy link

codecov bot commented Aug 6, 2020

Codecov Report

Merging #102 into develop will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff            @@
##           develop     #102   +/-   ##
========================================
  Coverage    95.33%   95.33%           
========================================
  Files           22       22           
  Lines         1223     1223           
========================================
  Hits          1166     1166           
  Misses          57       57           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a31e5cf...60be7a0. Read the comment docs.

@bassoy
Copy link
Collaborator

bassoy commented Aug 12, 2020

@coder3101
I think it would make sense to have a Github-Action for the CMAKE on a windows and linux machine.

@coder3101
Copy link
Contributor Author

Okay, I will add it after my CMake PR is merged.

@bassoy bassoy merged commit 92177ce into boostorg:develop Aug 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants