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

chore: replace Travis CI with Github Actions #89

Merged

Conversation

QQism
Copy link
Contributor

@QQism QQism commented May 27, 2022

This commit adds GHA files for CI, Danger, and Rubocop and removes
travis configurations.

Note: Ruby 2.5.0 is broken with specs. Consider to drop its support
since it's already EOL.

It seems working fine here QQism#1

QQism added 3 commits May 27, 2022 07:42
Otherwise, it's broken when running on Github Actions
This commit adds GHA files for CI, Danger, and Rubocop and removes
travis configurations.

Note: Ruby 2.5.0 is broken with specs. Consider to drop its support
since it's already EOL.
@QQism QQism changed the title feat: use GitHub actions instead of travis chore: use GitHub actions instead of travis May 27, 2022
@QQism QQism marked this pull request as ready for review May 27, 2022 00:36
- 2.7.2
- 3.0.0
- ruby-head
- jruby-9.1.17
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have to pump this to jruby-9.1.17 since ubuntu-latest doesn't have jruby-9.1.16.0. See this

@QQism QQism changed the title chore: use GitHub actions instead of travis chore: replace Travis CI with Github Actions May 27, 2022
Copy link
Collaborator

@dblock dblock left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm going to merge this, but I think danger is going to be broken. We can fix on top, give another PR a try to see it work/fail?

jobs:
test:
runs-on: ubuntu-latest
continue-on-error: ${{ contains(fromJSON('["2.5.0", "ruby-head", "jruby-9.1", "jruby-head"]'), matrix.ruby-version) }}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would just set this to true/false

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, that would be much simpler. I wanted to stay close to the old travis.yml as much as possible i.e. ruby-head, jruby-9.1 and jruby-head are optional steps.

danger_file: 'Dangerfile'
danger_id: 'danger-pr'
env:
DANGER_GITHUB_API_TOKEN: ${{ secrets.GITHUB_TOKEN }}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, turned out it only worked in my fork but not in this main repository. I've just updated with your example. Can you please have a look here?

@dblock dblock merged commit 9248749 into ashkan18:master Jun 5, 2022
@dblock
Copy link
Collaborator

dblock commented Jun 5, 2022

Thank you! Make another PR that drops Ruby 2.5.0, and checks Danger?

QQism added a commit to QQism/graphlient that referenced this pull request Jun 7, 2022
By default, `GITHUB_TOKEN` from a fork repository doesn't have write
permission to the current pull request, so we have to use a personal
token.

See:
ashkan18#89 (comment)
QQism added a commit to QQism/graphlient that referenced this pull request Jun 7, 2022
By default, `GITHUB_TOKEN` from a fork repository doesn't have write
permission to the current pull request, so we have to use a personal
token.

See:
ashkan18#89 (comment)
QQism added a commit to QQism/graphlient that referenced this pull request Jun 7, 2022
By default, `GITHUB_TOKEN` from a fork repository doesn't have write
permission to the current pull request, so we have to use a personal
token.

See:
ashkan18#89 (comment)
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