ucsf-education/zorgbort

Zorgbort does Iliosy things well

ZORGBORT (an Ilios bot)

Zorgbort is going to make common tasks easier to do.

Running Locally:

You'll need a publicly-accessible address to configure Slack OAuth. You can create a tunnel with https://ngrok.com and run ngrok http 3000 to connect.

You'll need to configure a Slack app to test with at https://api.slack.com/apps. This will give you the details to fill in for your .env file.

1. git clone zorgbort
2. npm install
3. add a .env file with:

SLACK_SIGNING_SECRET="SECRET"
SLACK_BOT_TOKEN="TOKEN"
GITHUB_TOKEN="TOKEN"
VALID_RELEASE_USERS="SLACKID,SLACKID2"
PORT=3000

4. Run ZORGBORT with npm start

Acknowledgments

• Release Notes idea and format from github-changelog-generator

zorgbort's Issues

An in-range update of mocha is breaking the build 🚨

Version 3.4.0 of mocha just got published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	3.3.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

v3.4.0

Mocha is now moving to a quicker release schedule: when non-breaking changes are merged, a release should happen that week.

This week's highlights:

• allowUncaught added to commandline as --allow-uncaught (and bugfixed)
• warning-related Node flags

🎉 Enhancements

• #2793, #2697: add --allowUncaught to Node.js (@lrowe)
• #2733: Add --no-warnings and --trace-warnings flags (@sonicdoe)

🐛 Fixes

• #2793, #2697: fix broken allowUncaught (@lrowe)

🔩 Other

• #2778: Add license report and scan status (@xizhao)
• #2794: no special case for macOS running Karma locally (@boneskull)
• #2795: reverts use of semistandard directly ([#2648]) (@boneskull)

Commits

The new version differs by 9 commits0.

• 7554b31 Add Changelog for v3.4.0
• 9f7f7ed Add --trace-warnings flag
• 92561c8 Add --no-warnings flag
• ceee976 lint test/integration/fixtures/simple-reporter.js
• dcfc094 Revert "use semistandard directly"
• 93392dd no special case for macOS running Karma locally
• 4d1d91d --allow-uncaught cli option
• fb1e083 fix allowUncaught in browser
• 4ed3fc5 Add license report and scan status

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of moment is breaking the build 🚨

Version 2.19.1 of moment was just published.

Branch	Build failing 🚨
Dependency	moment
Current Version	2.19.0
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

moment is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

PRs that are closed without merging appear in release notes

PRs should be checked for merged status before they are included.

An in-range update of eslint is breaking the build 🚨

Version 4.6.0 of eslint just got published.

Branch	Build failing 🚨
Dependency	eslint
Current Version	4.5.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

v4.6.0

• 56dd769 Docs: fix link format in prefer-arrow-callback.md (#9198) (Vse Mozhet Byt)
• 6becf91 Update: add eslint version to error output. (fixes #9037) (#9071) (薛定谔的猫)
• 0e09973 New: function-paren-newline rule (fixes #6074) (#8102) (Teddy Katz)
• 88a64cc Chore: Make parseJsonConfig() a pure function in Linter (#9186) (Teddy Katz)
• 1bbac51 Fix: avoid breaking eslint-plugin-eslint-comments (fixes #9193) (#9196) (Teddy Katz)
• 3e8b70a Fix: off-by-one error in eslint-disable comment checking (#9195) (Teddy Katz)
• 73815f6 Docs: rewrite prefer-arrow-callback documentation (fixes #8950) (#9077) (Charles E. Morgan)
• 0d3a854 Chore: avoid mutating report descriptors in report-translator (#9189) (Teddy Katz)
• 2db356b Update: no-unused-vars Improve message to include the allowed patterns (#9176) (Eli White)
• 8fbaf0a Update: Add configurability to generator-star-spacing (#8985) (Ethan Rutherford)
• 8ed779c Chore: remove currentScopes property from Linter instances (refs #9161) (#9187) (Teddy Katz)
• af4ad60 Fix: Handle error when running init without npm (#9169) (Gabriel Aumala)
• 4b94c6c Chore: make parse() a pure function in Linter (refs #9161) (#9183) (Teddy Katz)
• 1be5634 Chore: don't make Linter a subclass of EventEmitter (refs #9161) (#9177) (Teddy Katz)
• e95af9b Chore: don't include internal test helpers in npm package (#9160) (Teddy Katz)
• 6fb32e1 Chore: avoid using private Linter APIs in astUtils tests (refs #9161) (#9173) (Teddy Katz)
• de6dccd Docs: add documentation for Linter methods (refs #6525) (#9151) (Teddy Katz)
• 2d90030 Chore: remove unused assignment. (#9182) (薛定谔的猫)
• d672aef Chore: refactor reporting logic (refs #9161) (#9168) (Teddy Katz)
• 5ab0434 Fix: indent crash on sparse arrays with "off" option (fixes #9157) (#9166) (Teddy Katz)
• c147b97 Chore: Make SourceCodeFixer accept text instead of a SourceCode instance (#9178) (Teddy Katz)
• f127423 Chore: avoid using private Linter APIs in Linter tests (refs #9161) (#9175) (Teddy Katz)
• 2334335 Chore: avoid using private Linter APIs in SourceCode tests (refs #9161) (#9174) (Teddy Katz)
• 2dc243a Chore: avoid using internal Linter APIs in RuleTester (refs #9161) (#9172) (Teddy Katz)
• d6e436f Fix: no-extra-parens reported some parenthesized IIFEs (fixes #9140) (#9158) (Teddy Katz)
• e6b115c Build: Add an edit link to the rule docs’ metadata (#9049) (Jed Fox)
• fcb7bb4 Chore: avoid unnecessarily complex forEach calls in no-extra-parens (#9159) (Teddy Katz)
• ffa021e Docs: quotes rule - when does \n require backticks (#9135) (avimar)
• 60c5148 Chore: improve coverage in lib/*.js (#9130) (Teddy Katz)

Commits

The new version differs by 31 commits.

• 8f01a99 4.6.0
• c0acbf2 Build: changelog update for 4.6.0
• 56dd769 Docs: fix link format in prefer-arrow-callback.md (#9198)
• 6becf91 Update: add eslint version to error output. (fixes #9037) (#9071)
• 0e09973 New: function-paren-newline rule (fixes #6074) (#8102)
• 88a64cc Chore: Make parseJsonConfig() a pure function in Linter (#9186)
• 1bbac51 Fix: avoid breaking eslint-plugin-eslint-comments (fixes #9193) (#9196)
• 3e8b70a Fix: off-by-one error in eslint-disable comment checking (#9195)
• 73815f6 Docs: rewrite prefer-arrow-callback documentation (fixes #8950) (#9077)
• 0d3a854 Chore: avoid mutating report descriptors in report-translator (#9189)
• 2db356b Update: no-unused-vars Improve message to include the allowed patterns (#9176)
• 8fbaf0a Update: Add configurability to generator-star-spacing (#8985)
• 8ed779c Chore: remove currentScopes property from Linter instances (refs #9161) (#9187)
• af4ad60 Fix: Handle error when running init without npm (#9169)
• 4b94c6c Chore: make parse() a pure function in Linter (refs #9161) (#9183)

There are 31 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of app-root-path is breaking the build 🚨

Version 2.1.0 of app-root-path was just published.

Branch	Build failing 🚨
Dependency	[app-root-path](https://github.com/inxilpro/node-app-root-path)
Current Version	2.0.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

app-root-path is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Commits

The new version differs by 3 commits.

• 2339037 Merge pull request #24 from jrtipton/aws-lambda
• cead96b feat: Support AWS Lambda execution environment
• aec6a8f chore(package): Added add'l files to .npmignore

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

update serverless@2 to serverless@3

Update serverless@2 to serverless@3.

https://www.serverless.com/framework/docs/guides/upgrading-v3

You will want to update serverless-offline to 8.4.0 to avoid peer dependency issues. I'll open that PR right now.

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• The engines config in 1 of your package.json files was updated to the new Node.js version

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

regression: user id shown instead of user name

fix this.

Offer A Confirmation Option Before Releasing an Update

This is just to make sure the correct release version/level has been selected before actually running the release. After "release type" has been selected, offer a confirmation of this to be certain. I know it's an extra step but currently as soon as you select the release type, it runs instantly.

preview release notes before selection release type

As part of the release process, the user gets prompted to pick which type of release should be published.

To assist in this decision making, it would be helpful to preview the release notes (the change log between the latest release and current HEAD of master) in that dialog.

The functionality for generating release notes already exists and should be reused.

serverless deprecation

This is showing up in our GitHub Actions output:

2022-02-03T21:36:47.7422016Z 1 deprecation found: run 'serverless doctor' for more details

Ignore wont fix labled tickets

These shouldn't appear as resolved issues.

update lock file with new version

currently, this needs to be handled post-release manually.

see ilios/common#613 and ilios/frontend#4472 for examples.

not sure if this is even doable, just throwing it out there as an idea.