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

Blacklist/whitelist workflows via git commit messages #659

Merged
merged 4 commits into from
May 30, 2019

Conversation

JayjeetAtGithub
Copy link
Collaborator

Addresses #565

@pep8speaks
Copy link

pep8speaks commented May 28, 2019

Hello @JayjeetAtGithub! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻

Comment last updated at 2019-05-30 14:15:34 UTC

@JayjeetAtGithub JayjeetAtGithub force-pushed the jayjeet/blacklist branch 2 times, most recently from 870aad9 to c881423 Compare May 29, 2019 08:26
@JayjeetAtGithub
Copy link
Collaborator Author

JayjeetAtGithub commented May 29, 2019

@ivotron Can you please explain how to deal with merge commits ? Thanks


if 'Merge' in msg:
log.info("Merge detected. Reading message from merged commit.")
commit_id = re.search(r'Merge (.+?) into', msg).group(1)
Copy link
Collaborator

@ivotron ivotron May 29, 2019

Choose a reason for hiding this comment

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

a merge commit is a "meta-commit" that describes a commit commit A being merged into B. For example, this one. The idea is to obtain the message for A, which is the commit that is being merged, and process it so that we know whether there are any workflows being white/black listed. Since we are now using GitPython, we might be able to use it to obtain this information (as opposed to using regular expressions.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Thanks !

@JayjeetAtGithub JayjeetAtGithub changed the title Fixes #565 blacklist/whitelist workflows via git commit messages May 30, 2019
@JayjeetAtGithub JayjeetAtGithub changed the title blacklist/whitelist workflows via git commit messages Blacklist/whitelist workflows via git commit messages May 30, 2019
@JayjeetAtGithub
Copy link
Collaborator Author

JayjeetAtGithub commented May 30, 2019

@ivotron Please review. Thanks.

@ivotron ivotron merged commit 69694bf into getpopper:master May 30, 2019
@ivotron
Copy link
Collaborator

ivotron commented May 30, 2019

awesome! Thanks a lot!

@JayjeetAtGithub JayjeetAtGithub deleted the jayjeet/blacklist branch May 31, 2019 08:21
ivotron pushed a commit that referenced this pull request May 24, 2020
Adds the ability to blacklist/whitelist which workflows to execute based on keywords found in a Git commit message.

fixes #565
ivotron pushed a commit that referenced this pull request May 25, 2020
Adds the ability to blacklist/whitelist which workflows to execute based on keywords found in a Git commit message.

fixes #565
ivotron pushed a commit that referenced this pull request May 25, 2020
Adds the ability to blacklist/whitelist which workflows to execute based on keywords found in a Git commit message.

fixes #565
ivotron pushed a commit that referenced this pull request May 25, 2020
Adds the ability to blacklist/whitelist which workflows to execute based on keywords found in a Git commit message.

fixes #565
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.

None yet

3 participants