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.

Sign up for GitHub

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

Jump to bottom

Enhance: condition order for api call optimisation #32

Open
lmarvaud opened this issue Nov 16, 2020 · 3 comments · May be fixed by #296
Open

Enhance: condition order for api call optimisation #32

lmarvaud opened this issue Nov 16, 2020 · 3 comments · May be fixed by #296
Assignees
@ncalteen

Comments

@lmarvaud
Copy link

Hello,

Little enhance :

The condition if no message set should be place before the condition if its not their first contribution

That would avoid some useless api calls.

Best regards,
Léni
@masterful
Copy link

I believe #30 would address this, right?

@lmarvaud
Copy link
Author

I believe #30 would address this, right?

Absolutely

@ncalteen ncalteen self-assigned this Feb 22, 2024
@ncalteen
Copy link
Collaborator

This should also be addressed in #296 :) (Apologies for the lack of response, I'm doing cleanup of some of the actions repos and bringing things up to date)

@ncalteen ncalteen linked a pull request Feb 22, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ncalteen ncalteen

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Standardize Action ncalteen/first-interaction
3 participants
@masterful @ncalteen @lmarvaud