-
Updated
Dec 19, 2020 - JavaScript
slack
Here are 4,690 public repositories matching this topic...
-
Updated
Dec 19, 2020 - Clojure
It's useful to know. This request came through support.
-
Updated
Dec 15, 2020 - TypeScript
-
Updated
Dec 14, 2020 - JavaScript
What went wrong?
I'm getting deprecation warnings with openSSL encryption.
[2019/09/05 08:38:52][info] Using Encryptor::OpenSSL to encrypt the archive.
[2019/09/05 08:40:22][warn] Pipeline STDERR Messages:
[2019/09/05 08:40:22][warn] (Note: may be interleaved if multiple commands returned error messages)
[2019/09/05 08:40:22][warn]
[2019/09/05 08:40:22][warn] *** WARNING : depre
-
Updated
Dec 14, 2020 - JavaScript
-
Updated
Dec 18, 2020 - Go
-
Updated
Nov 11, 2019 - Python
-
Updated
Dec 17, 2020 - Go
Currently, the integration tests still use slack package and verify if the WebClient and so on under the package works. As the source code is automatically generated from slack_sdk.web.WebClient, this is still good enough at this point. However, ideally we can use slack_sdk package for the tests and have additional tests for slack package.
Category (place an x in each of the [ ]
Description
It's a best practice to always provide a text argument when posting a message, even though the platform doesn't technically require it when blocks are provided. The text argument is used in places where blocks cannot be rendered such as: system push notifications, assistive technology such as screen readers, etc.
In order to help apps adhere to this best practice and
-
Updated
Jun 21, 2020
Problem
We want to limit data retention for users in our hosted free tier. Let's start by archiving conversations that haven't been active in >30 days and are not marked as a priority (i.e. favorited/starred).
Solution
Create a worker with Oban (example) that archives conversations where the
Describe the feature
Reduce the BigQuery OAuth scopes down to the minimal set needed, in both dbt and dbt Cloud.
Additional context
Currently, the dbt BigQuery connector requests these three OAuth scopes:
- 'https://www.googleapis.com/auth/bigquery'
- 'https://www.googleapis.com/auth/cloud-platform'
- 'https://www.googleapis.com/auth/drive'
The BigQuery scope is needed to a
Description
This repository's TravisCI build settings no longer work. We are planning to migrate to GitHub Actions before the next release.
What type of issue is this? (place an x in one of the [ ])
- bug
- enhancement (feature request)
- question
- documentation related
- testing related
- discussion
Requirements (place an x in each of the
I try to switch from RamBox to Ferdi. However I have several services with the same icon (slack, nextcloud). It would be a great help if I just cloud add a small textual label next to, under, over the icon. Don't care where.
Sorry that this is not a pull request, my JS/css knowledge is insufficient. I tried copying the tooltip to a div. Didn't get the correct tooltip and a misplaced div...
-
Updated
Mar 26, 2020 - Swift
-
Updated
Jul 30, 2019 - CSS
Since adding integration with a number of other external systems, the landing README.md has become a bit cluttered. In addition to that, there's not a lot of detail on some of these integrations (versions,etc.).
What I'd like to do is break up some of the documentation for this and also add some information on what versions of the integrations are supported/tested.
Improve this page
Add a description, image, and links to the slack topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the slack topic, visit your repo's landing page and select "manage topics."
We should display a notice on whether the user's email address will be public to other members of the organization (according to the "Email address visibility" setting) on the account registration page. I'm not sure what the best visuals are for this; options include:
?icon with a popover explaining this detail next to the "Email" fieldText c