-
Notifications
You must be signed in to change notification settings - Fork 200
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
Changing the commit message to 1000 characters #296
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!!
This PR is idle because it has been open for 14 days with no activity. |
Any plans to merge this one? This issue is intermittently blocking our pipelines, would love to see progress 🙏 |
@AaronL1011 Could you share the debug logs of the failed runs? I had tried reproducing same last week and it wasn't failing for me with existing limit? |
Added an example of it failing in #288. |
Unfortunately its all under private repos, and I can't share the entire action run, however it's virtually the same as the failing action @Methuselah96 has shared. Ive attached as much of the log as possible, the zipdeploy URL was ~2159 chars long.
|
lib/actionparameters.js
Outdated
@@ -37,7 +37,7 @@ class ActionParameters { | |||
/** | |||
* Trimming the commit message because it is used as a param in uri of deployment api. And sometimes, it exceeds the max length of http URI. | |||
*/ | |||
this._commitMessage = github.context.eventName === 'push' ? github.context.payload.head_commit.message.slice(0, 7000) : ""; | |||
this._commitMessage = github.context.eventName === 'push' ? github.context.payload.head_commit.message.slice(0, 2000) : ""; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM !!
This PR is idle because it has been open for 14 days with no activity. |
This looks good to me too, and appears like it should resolve #288. Still waiting on something before merging? |
Yeah keen to get this one on the move, is there a hold up in the deploy pipeline process? Not sure who is the right person to push this through. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This PR is covered as part of #301. |
This covers #288.
Recently we found out that 7000 doesn't work in some scenarios intermittently, keeping it a bit lower for the deployment to go through.