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

Allow Keyword - PR #213 followup #214

Merged

Conversation

steeve85
Copy link
Contributor

This is to follow up on #213

  • I have updated the README
  • I added a Test for allowed pattern at the file and repository level
  • I have updated the string used to replace allowed keywords
  • I added omitempty option on FileIgnoreConfig.Checksum as I believe this is not a required parameter (This might need additional testing 👀 cc @svishwanath-tw @harinee )

@svishwanath-tw svishwanath-tw merged commit 27bc869 into thoughtworks:master Jul 25, 2020
@steeve85
Copy link
Contributor Author

When is your next release scheduled for?
I'd like to have my users using this new "allow pattern" feature, but I think it requires a new release from the repo owner to have users setup being automatically updated with the new Talisman version

harinee pushed a commit to harinee/talisman that referenced this pull request Aug 9, 2020
I have updated the README
I added a Test for allowed pattern at the file and repository level
I have updated the string used to replace allowed keywords
I added omitempty option on FileIgnoreConfig.Checksum as I believe this is not a required parameter (This might need additional testing 👀 cc @svishwanath-tw @harinee )
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