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

Set API token in SlackNotificationConfig#getAsElement, fixes #86 #122

Merged
merged 1 commit into from
Aug 19, 2016

Conversation

tonybaroneee
Copy link
Contributor

For backwards-compatibility, allows configs to be read/written without a token set. Includes test updates as well.

This reverts commit 4b8cb62.

@tonybaroneee
Copy link
Contributor Author

@pointerxr Ok, here's the updated PR with fixed tests and a slightly more robust implementation (makes sure token is not null before attempting to setAttribute).

@marvin-w
Copy link
Collaborator

Thanks +1 for the fast resolve

@tonybaroneee
Copy link
Contributor Author

Thank you for the quick merge! Any idea on a timeframe for a release?

@marvin-w
Copy link
Collaborator

Unfortunately I don't have permissions to release a new version. Furthermore it seems that Pete, the owner, is no longer participating here.

Also as I planned the refactor almost the complete codebase I do believe that I fork this project in the future and maintain it myself if Pete doesn't reply anymore.

@tonybaroneee
Copy link
Contributor Author

Ah, understood. Thanks for the heads up.

@marvin-w
Copy link
Collaborator

I got some time today so I might set it up accordingly after I tried to reach Pete again to give me appropriate permissions or release it.

@marvin-w
Copy link
Collaborator

https://github.com/PeteGoo/tcSlackBuildNotifier/releases/tag/v1.4.6

have fun!

@tonybaroneee
Copy link
Contributor Author

Thank you so much!!

@marvin-w
Copy link
Collaborator

You're welcome. Can you tell me which issues are currently most requested? I got some time left to do some of them.

@tonybaroneee
Copy link
Contributor Author

No clue :) This was the only issue that was burning us after server restarts, so glad we could get a fix in so quickly.

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