Action #1
Action #1
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Conventional commit lint
This repository uses conventional commits, the following issues were found:
⛔ Commit f3b2bef by Carlos Colaço:
Message: Merge 0805936 into 9cc4f77
Issues found:
- invalid header format. Expected: type(optional scope): description
What can you do now?
There are more than one way of fixing this issues, using a interactive rebase (git rebase -i <target branch>) to reword/squash your commits and then force pushing towards your branch / fork is probably the most adequate.
coolapso
force-pushed
the
action
branch
2 times, most recently
from
0085c56 to
8d46c8c
Compare
There was a problem hiding this comment.
Conventional commit lint
This repository uses conventional commits, the following issues were found:
⛔ Commit 2841ced by Carlos Colaço:
Message: Merge 8d46c8c into 9cc4f77
Issues found:
- invalid header format. Expected: type(optional scope): description
What can you do now?
There are more than one way of fixing this issues, using a interactive rebase (git rebase -i <target branch>) to reword/squash your commits and then force pushing towards your branch / fork is probably the most adequate.
There was a problem hiding this comment.
Conventional commit lint
This repository uses conventional commits, the following issues were found:
⛔ Commit 0d1e9db by Carlos Colaço:
Message: Merge 250e1a2 into 9cc4f77
Issues found:
- invalid header format. Expected: type(optional scope): description
What can you do now?
There are more than one way of fixing this issues, using a interactive rebase (git rebase -i <target branch>) to reword/squash your commits and then force pushing towards your branch / fork is probably the most adequate.
There was a problem hiding this comment.
Conventional commit lint
This repository uses conventional commits, the following issues were found:
⛔ Commit 0f4894a by Carlos Colaço:
Message: Merge 1c3da09 into 9cc4f77
Issues found:
- invalid header format. Expected: type(optional scope): description
What can you do now?
There are more than one way of fixing this issues, using a interactive rebase (git rebase -i <target branch>) to reword/squash your commits and then force pushing towards your branch / fork is probably the most adequate.
There was a problem hiding this comment.
Conventional commit lint
This repository uses conventional commits, the following issues were found:
⛔ Commit 1aea729 by Carlos Colaço:
Message: Add fetch
Issues found:
- invalid header format. Expected: type(optional scope): description
⛔ Commit cee7ecd by Carlos Colaço:
Message: fix headref
Issues found:
- invalid header format. Expected: type(optional scope): description
⛔ Commit 8b33ccb by Carlos Colaço:
Message: head ref
Issues found:
- invalid header format. Expected: type(optional scope): description
⛔ Commit 1c3da09 by Carlos Colaço:
Message: fetch depth 0
Issues found:
- invalid header format. Expected: type(optional scope): description
⛔ Commit 250e1a2 by Carlos Colaço:
Message: test checkoug refname
Issues found:
- invalid header format. Expected: type(optional scope): description
⛔ Commit 8d46c8c by Carlos Colaço:
Message: test wihtout depth
Issues found:
- invalid header format. Expected: type(optional scope): description
⛔ Commit 2a77c77 by Carlos Colaço:
Message: remove continue on error
Issues found:
- invalid header format. Expected: type(optional scope): description
⛔ Commit b42e52a by Carlos Colaço:
Message: Fix action.yaml to publish on marketplace
Issues found:
- invalid header format. Expected: type(optional scope): description
What can you do now?
There are more than one way of fixing this issues, using a interactive rebase (git rebase -i <target branch>) to reword/squash your commits and then force pushing towards your branch / fork is probably the most adequate.
There was a problem hiding this comment.
Conventional commit lint
This repository uses conventional commits, the following issues were found:
⛔ Commit f7dde33 by Carlos Colaço:
Message: fix local path
Issues found:
- invalid header format. Expected: type(optional scope): description
⛔ Commit 50705ec by Carlos Colaço:
Message: run action locally
Issues found:
- invalid header format. Expected: type(optional scope): description
⛔ Commit 2295f92 by Carlos Colaço:
Message: Mske action do checkout to make sure it gets history right
Issues found:
- invalid header format. Expected: type(optional scope): description
⛔ Commit 1aea729 by Carlos Colaço:
Message: Add fetch
Issues found:
- invalid header format. Expected: type(optional scope): description
⛔ Commit cee7ecd by Carlos Colaço:
Message: fix headref
Issues found:
- invalid header format. Expected: type(optional scope): description
⛔ Commit 8b33ccb by Carlos Colaço:
Message: head ref
Issues found:
- invalid header format. Expected: type(optional scope): description
⛔ Commit 1c3da09 by Carlos Colaço:
Message: fetch depth 0
Issues found:
- invalid header format. Expected: type(optional scope): description
⛔ Commit 250e1a2 by Carlos Colaço:
Message: test checkoug refname
Issues found:
- invalid header format. Expected: type(optional scope): description
⛔ Commit 8d46c8c by Carlos Colaço:
Message: test wihtout depth
Issues found:
- invalid header format. Expected: type(optional scope): description
⛔ Commit 2a77c77 by Carlos Colaço:
Message: remove continue on error
Issues found:
- invalid header format. Expected: type(optional scope): description
⛔ Commit b42e52a by Carlos Colaço:
Message: Fix action.yaml to publish on marketplace
Issues found:
- invalid header format. Expected: type(optional scope): description
What can you do now?
There are more than one way of fixing this issues, using a interactive rebase (git rebase -i <target branch>) to reword/squash your commits and then force pushing towards your branch / fork is probably the most adequate.
There was a problem hiding this comment.
Conventional commit lint
This repository uses conventional commits, the following issues were found:
⛔ Commit e9b53ff by Carlos Colaço:
Message: Final test
Issues found:
- invalid header format. Expected: type(optional scope): description
What can you do now?
There are more than one way of fixing this issues, using a interactive rebase (git rebase -i <target branch>) to reword/squash your commits and then force pushing towards your branch / fork is probably the most adequate.
coolapso
force-pushed
the
action
branch
2 times, most recently
from
d0bc75a to
3e67124
Compare
Use checkout inside the action to correctly fetch the git history Fetch base branch tip commit Set only necessary flags, all other flags can be controled thru ENV variables
Running workflow directly from local repository to make development & fixes easier
No description provided.