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

Add deploy message #40

Merged
merged 1 commit into from
Mar 3, 2020
Merged

Add deploy message #40

merged 1 commit into from
Mar 3, 2020

Conversation

South-Paw
Copy link
Contributor

Description

  • Added deploy-message param to the action
    • Allows for a custom deploy message to be set when triggering a build in Netlify

@South-Paw
Copy link
Contributor Author

South-Paw commented Mar 3, 2020

@nwtgck I can't really justify putting in any more hours than I already have to this PR - so hopefully this is good enough

@nwtgck
Copy link
Owner

nwtgck commented Mar 3, 2020

@South-Paw Yes. I think so too. I'll merge this after I use this feature.

@nwtgck
Copy link
Owner

nwtgck commented Mar 3, 2020

Reports

Successfully deployed without deploy-comment

c371ee6

image

Successfully deployed with deploy-comment

1bf0919#comments

image

I set "Deploy from GitHub Actions" because the commit is not PR. The time is JST.

@nwtgck
Copy link
Owner

nwtgck commented Mar 3, 2020

@South-Paw Thank you very much for this feature.

I'll merge this now. I use "Deploy from GitHub Actions" in README.md sample because not only PR triggers Netlify deploy.

@nwtgck nwtgck merged commit b1a6e85 into nwtgck:develop Mar 3, 2020
@nwtgck
Copy link
Owner

nwtgck commented Mar 3, 2020

@South-Paw I released 1.0.5 including this feature 🎉
https://github.com/nwtgck/actions-netlify/releases/tag/v1.0.5
You can use this with tag v1.0 and v1.0.5. Thank you very much!

@South-Paw South-Paw deleted the add-deploy-message-2 branch March 3, 2020 06:19
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