Skip to content
This repository has been archived by the owner on Apr 11, 2022. It is now read-only.

Add more test #28

Merged
merged 46 commits into from
Aug 16, 2020
Merged

Add more test #28

merged 46 commits into from
Aug 16, 2020

Conversation

shiipou
Copy link
Member

@shiipou shiipou commented Aug 16, 2020

This allow to test v fmt and v build

This allow to test `v fmt` and `v build`
@shiipou shiipou added this to the Release v1 milestone Aug 16, 2020
@shiipou shiipou requested a review from a team August 16, 2020 17:31
@shiipou shiipou self-assigned this Aug 16, 2020
@shiipou shiipou removed the request for review from a team August 16, 2020 17:31
@shiipou shiipou changed the title Add more test WIP: Add more test Aug 16, 2020
@shiipou shiipou changed the title WIP: Add more test Add more test Aug 16, 2020
@shiipou shiipou requested a review from a team August 16, 2020 19:37
@shiipou shiipou merged commit 83742e7 into master Aug 16, 2020
@shiipou shiipou deleted the shiipou-patch-1 branch August 16, 2020 19:39
- name: Test V is present
run: v version

- name: Test V fmt
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why do we need to test V commands here? It's enough to run v version and ${{ steps.v.outputs.v_home }}/v version to make sure V executable is visible.

Copy link
Member Author

Choose a reason for hiding this comment

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

Because I've got one people where the command v fmt -verify does not work when using the action.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants