Skip to content

Conversation

@jimsynz
Copy link
Contributor

@jimsynz jimsynz commented Dec 28, 2020

This is handy because you can use dotenv files to share outputs between jobs on Gitlab CI.

Contributor checklist

  • My commit messages follow the Conventional Commit Message Format
    For example: fix: Multiply by appropriate coefficient, or
    feat(Calculator): Correctly preserve history
    Any explanation or long form information in your commit message should be
    in a separate paragraph, separated by a blank line from the primary message
  • Bug fixes include regression tests
  • Features include unit/acceptance tests

… info output.

This is handy because you can use `dotenv` files to share outputs between jobs on Gitlab CI.
@coveralls
Copy link

Pull Request Test Coverage Report for Build 159

  • 3 of 4 (75.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+2.5%) to 85.574%

Changes Missing Coverage Covered Lines Changed/Added Lines %
lib/mix/tasks/git_ops.project_info.ex 3 4 75.0%
Totals Coverage Status
Change from base Build 157: 2.5%
Covered Lines: 261
Relevant Lines: 305

💛 - Coveralls

Copy link
Owner

@zachdaniel zachdaniel left a comment

Choose a reason for hiding this comment

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

Looks great, thanks!

🚀 Thank you for your contribution! 🚀

@zachdaniel zachdaniel merged commit 97a69fa into zachdaniel:master Dec 28, 2020
@jimsynz jimsynz deleted the add-dotenv-format branch December 28, 2020 05:14
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.

3 participants