You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: .github/ISSUE_TEMPLATE/feature_request.md
+2
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,9 @@ assignees: ""
49
49
(Share it here.)
50
50
51
51
---
52
+
52
53
##### House rules
54
+
53
55
- If this issue has a `🚨 needs approval` label, don't start coding yet. Wait until a core member approves feature request by removing this label, then you can start coding.
54
56
- For clarity: Non-core member issues automatically get the `🚨 needs approval` label.
55
57
- Your feature ideas are invaluable to us! However, they undergo review to ensure alignment with the product's direction.
Copy file name to clipboardexpand all lines: CONTRIBUTING.md
+12-9
Original file line number
Diff line number
Diff line change
@@ -177,24 +177,25 @@ Do not commit your `yarn.lock` unless you've made changes to the `package.json`.
177
177
178
178
If your last commit has the `yarn.lock` file alongside other files and you only wish to uncommit the `yarn.lock`:
179
179
180
-
```bash
181
-
git checkout HEAD~1 yarn.lock
182
-
git commit -m "Revert yarn.lock changes"
183
-
```
180
+
```bash
181
+
git checkout HEAD~1 yarn.lock
182
+
git commit -m "Revert yarn.lock changes"
183
+
```
184
184
185
185
_NB_: You may have to bypass the pre-commit hook with by appending `--no-verify` to the git commit
186
186
If you've pushed the commit with the `yarn.lock`:
187
187
188
-
1. Correct the commit locally using the above method.
189
-
2. Carefully force push:
188
+
1. Correct the commit locally using the above method.
189
+
2. Carefully force push:
190
190
191
-
```bash
192
-
git push origin <your-branch-name> --force
193
-
```
191
+
```bash
192
+
git push origin <your-branch-name> --force
193
+
```
194
194
195
195
If `yarn.lock` was committed a while ago and there have been several commits since, you can use the following steps to revert just the `yarn.lock` changes without impacting the subsequent changes:
196
196
197
197
1.**Checkout a Previous Version**:
198
+
198
199
- Find the commit hash before the `yarn.lock` was unintentionally committed. You can do this by viewing the Git log:
199
200
200
201
```bash
@@ -208,13 +209,15 @@ If `yarn.lock` was committed a while ago and there have been several commits sin
208
209
```
209
210
210
211
2. **Commit the Reverted Version**:
212
+
211
213
- After checking out the previous version of the `yarn.lock`, commit this change:
212
214
213
215
```bash
214
216
git commit -m "Revert yarn.lock to its state before unintended changes"
215
217
```
216
218
217
219
3. **Proceed with Caution**:
220
+
218
221
- If you need to push this change, first pull the latest changes from your remote branch to ensure you're not overwriting other recent changes:
Copy file name to clipboardexpand all lines: README.md
+22-22
Original file line number
Diff line number
Diff line change
@@ -175,7 +175,7 @@ yarn dx
175
175
176
176
Add `NEXT_PUBLIC_LOGGER_LEVEL={level}` to your .env file to control the logging verbosity for all tRPC queries and mutations.\
177
177
Where {level} can be one of the following:
178
-
178
+
179
179
`0` for silly \
180
180
`1` for trace \
181
181
`2` for debug \
@@ -187,14 +187,14 @@ Where {level} can be one of the following:
187
187
When you set `NEXT_PUBLIC_LOGGER_LEVEL={level}` in your .env file, it enables logging at that level and higher. Here's how it works:
188
188
189
189
The logger will include all logs that are at the specified level or higher. For example: \
190
+
190
191
- If you set `NEXT_PUBLIC_LOGGER_LEVEL=2`, it will log from level 2 (debug) upwards, meaning levels 2 (debug), 3 (info), 4 (warn), 5 (error), and (fatal) will be logged. \
191
192
- If you set `NEXT_PUBLIC_LOGGER_LEVEL=3`, it will log from level 3 (info) upwards, meaning levels 3 (info), 4 (warn), 5 (error), and 6 (fatal) will be logged, but level 2 (debug) and level 1 (trace) will be ignored. \
192
193
193
-
194
-
195
194
```sh
196
195
echo'NEXT_PUBLIC_LOGGER_LEVEL=3'>> .env
197
196
```
197
+
198
198
for Logger level to be set at info, for example.
199
199
200
200
#### Gitpod Setup
@@ -417,25 +417,25 @@ Cal.com, Inc. is a commercial open source company, which means some parts of thi
417
417
> [!NOTE]
418
418
> Our philosophy is simple, all "Singleplayer APIs" are open-source under AGPLv3. All commercial "Multiplayer APIs" are under a commercial license.
419
419
420
-
|| AGPLv3 | EE |
421
-
|---|---|---|
422
-
| Self-host for commercial purposes| ✅ | ✅|
423
-
| Clone privately | ✅ | ✅ |
424
-
| Fork publicly | ✅ | ✅ |
425
-
| Requires CLA | ✅| ✅ |
426
-
| Official Support| ❌ | ✅ |
427
-
| Derivative work privately | ❌ | ✅ |
428
-
| SSO | ❌ | ✅ |
429
-
| Admin Panel | ❌ | ✅ |
430
-
| Impersonation | ❌ | ✅ |
431
-
| Managed Event Types | ❌ | ✅ |
432
-
| Organizations | ❌ | ✅ |
433
-
| Payments | ❌ | ✅ |
434
-
| Platform | ❌ | ✅ |
435
-
| Teams | ❌ | ✅ |
436
-
| Users | ❌ | ✅ |
437
-
| Video | ❌ | ✅ |
438
-
| Workflows | ❌ | ✅ |
420
+
|| AGPLv3 | EE |
421
+
|--------------------------------- |------ |---|
422
+
| Self-host for commercial purposes| ✅ | ✅ |
423
+
| Clone privately | ✅| ✅ |
424
+
| Fork publicly | ✅ | ✅|
425
+
| Requires CLA | ✅ | ✅ |
426
+
| Official Support| ❌ | ✅|
427
+
| Derivative work privately | ❌ | ✅|
428
+
| SSO | ❌ | ✅|
429
+
| Admin Panel | ❌ | ✅|
430
+
| Impersonation | ❌ | ✅|
431
+
| Managed Event Types | ❌ | ✅|
432
+
| Organizations | ❌ | ✅|
433
+
| Payments | ❌ | ✅|
434
+
| Platform | ❌ | ✅|
435
+
| Teams | ❌ | ✅|
436
+
| Users | ❌ | ✅|
437
+
| Video | ❌ | ✅|
438
+
| Workflows | ❌ | ✅|
439
439
440
440
> [!TIP]
441
441
> We work closely with the community and always invite feedback about what should be open and what is fine to be commercial. This list is not set and stone and we have moved things from commercial to open in the past. Please open a [discussion](https://github.com/calcom/cal.com/discussions) if you feel like something is wrong.
Copy file name to clipboardexpand all lines: example-apps/credential-sync/README.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -6,4 +6,5 @@ This is an example app that acts as the source of truth for Cal.com Apps credent
6
6
`yarn dev` starts the server on port 5100. After this open http://localhost:5100 and from there you would be able to manage the tokens for various Apps.
7
7
8
8
## Endpoints
9
-
http://localhost:5100/api/getToken should be set as the value of env variable CALCOM_CREDENTIAL_SYNC_ENDPOINT in Cal.com
9
+
10
+
http://localhost:5100/api/getToken should be set as the value of env variable CALCOM_CREDENTIAL_SYNC_ENDPOINT in Cal.com
This folder, located within the "infra" directory of our monorepo, is dedicated to managing the infrastructure as code (IaC) and Docker-related files for our project. It plays a critical role in orchestrating, configuring, and maintaining the infrastructure that our applications rely on.
3
2
3
+
This folder, located within the "infra" directory of our monorepo, is dedicated to managing the infrastructure as code (IaC) and Docker-related files for our project. It plays a critical role in orchestrating, configuring, and maintaining the infrastructure that our applications rely on.
Copy file name to clipboardexpand all lines: packages/app-store/linear/DESCRIPTION.md
+3
Original file line number
Diff line number
Diff line change
@@ -6,12 +6,15 @@ items:
6
6
{DESCRIPTION}
7
7
8
8
### Overview
9
+
9
10
The Linear integration with Google calendar allows you to connect your calendar and automate your status. If your teammates need to know whether you’re out of office, now they will.
10
11
11
12
### How it works
13
+
12
14
Once connected, your Linear status will detect out of office events in Google calendar and update your status when those events are upcoming or active.
13
15
14
16
### To Configure
17
+
15
18
Install Google Calendar from your Linear settings under My Account > Linked accounts.
16
19
17
20
Connect your account and sign into your Google account to allow access.
Copy file name to clipboardexpand all lines: packages/app-store/pipedrive-crm/README.md
+12-12
Original file line number
Diff line number
Diff line change
@@ -2,18 +2,18 @@
2
2
3
3
#### Obtaining Pipedrive Client ID and Secret
4
4
5
-
* Open [Pipedrive Developers Corner](https://developers.pipedrive.com/) and sign in to your account, or create a new one
6
-
* Go to Settings > (company name) Developer Hub
7
-
* Create a Pipedrive app, using the steps mentioned [here](https://pipedrive.readme.io/docs/marketplace-creating-a-proper-app#create-an-app-in-5-simple-steps)
8
-
* You can skip this step and use the default revert Pipedrive app
9
-
* Set `https://app.revert.dev/oauth-callback/pipedrive` as a callback url for your app
10
-
***Get your client\_id and client\_secret**:
11
-
* Go to the "OAuth & access scopes" tab of your app
12
-
* Copy your client\_id and client\_secret
5
+
- Open [Pipedrive Developers Corner](https://developers.pipedrive.com/) and sign in to your account, or create a new one
6
+
- Go to Settings > (company name) Developer Hub
7
+
- Create a Pipedrive app, using the steps mentioned [here](https://pipedrive.readme.io/docs/marketplace-creating-a-proper-app#create-an-app-in-5-simple-steps)
8
+
- You can skip this step and use the default revert Pipedrive app
9
+
- Set `https://app.revert.dev/oauth-callback/pipedrive` as a callback url for your app
10
+
-**Get your client_id and client_secret**:
11
+
- Go to the "OAuth & access scopes" tab of your app
12
+
- Copy your client_id and client_secret
13
13
14
14
#### Obtaining Revert API keys
15
15
16
-
* Create an account on Revert if you don't already have one. (https://app.revert.dev/sign-up)
17
-
* Login to your revert dashboard (https://app.revert.dev/sign-in) and click on `Customize your apps` - `Pipedrive`
18
-
* Enter the `client_id` and `client_secret` you copied in the previous step
19
-
* Enter the `client_id` and `client_secret` previously copied to `Settings > Admin > Apps > CRM > Pipedrive` by clicking the `Edit` button on the app settings.
16
+
- Create an account on Revert if you don't already have one. (https://app.revert.dev/sign-up)
17
+
- Login to your revert dashboard (https://app.revert.dev/sign-in) and click on `Customize your apps` - `Pipedrive`
18
+
- Enter the `client_id` and `client_secret` you copied in the previous step
19
+
- Enter the `client_id` and `client_secret` previously copied to `Settings > Admin > Apps > CRM > Pipedrive` by clicking the `Edit` button on the app settings.
Copy file name to clipboardexpand all lines: packages/app-store/roam/DESCRIPTION.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -3,14 +3,14 @@ items:
3
3
- 1.jpg
4
4
- 2.jpg
5
5
- 3.jpg
6
-
7
6
---
8
7
9
8
{DESCRIPTION}
10
9
11
10
Roam makes companies:
11
+
12
12
- more productive with shorter meetings
13
13
- more connected with a map that gives a feeling of working together without meeting
14
14
- & Roam saves companies money with our all-in-one bundle
15
15
16
-
When the whole company is in one HQ, productivity is high, people feel connected to the company. Calendars are emptied. Culture comes back. And companies using Roam benefit from our all-in-one approach to cut tools and save money.
16
+
When the whole company is in one HQ, productivity is high, people feel connected to the company. Calendars are emptied. Culture comes back. And companies using Roam benefit from our all-in-one approach to cut tools and save money.
Copy file name to clipboardexpand all lines: packages/app-store/synthflow/DESCRIPTION.md
-1
Original file line number
Diff line number
Diff line change
@@ -15,4 +15,3 @@ One of the best ways for a service business to create and close more customers i
15
15
1. Easily connect Cal.com with Synthflow using Cal.com API key.
16
16
2. Set up actions and define specific booking parameters tailored to your needs.
17
17
3. Attach the scheduling action to your assistant. Your AI Voice Assistants can now book appointments directly into live calendars and send instant notifications.
Copy file name to clipboardexpand all lines: packages/features/ee/organizations/README.md
+7-8
Original file line number
Diff line number
Diff line change
@@ -23,25 +23,25 @@ From the [Original RFC](https://github.com/calcom/cal.com/issues/7142):
23
23
1.`sudo npx hostile set localhost app.cal.local`
24
24
2. Add it yourself
25
25
26
-
6. Add `acme.cal.local` to host file given that the org create for it will be `acme`, otherwise do this for whatever slug will be assigned to the org. This is needed to test org-related public URLs, such as sub-teams, members and event-types.
26
+
4. Add `acme.cal.local` to host file given that the org create for it will be `acme`, otherwise do this for whatever slug will be assigned to the org. This is needed to test org-related public URLs, such as sub-teams, members and event-types.
27
27
28
-
7. Be sure to be logged in with any type of user and visit `/settings/organizations/new` and follow setup steps with the slug matching the org slug from step 3
28
+
5. Be sure to be logged in with any type of user and visit `/settings/organizations/new` and follow setup steps with the slug matching the org slug from step 3
29
29
30
-
8. Log in as admin and go to Settings and under Organizations you will need to accept the newly created organization in order to be operational
30
+
6. Log in as admin and go to Settings and under Organizations you will need to accept the newly created organization in order to be operational
31
31
32
-
9. After finishing the org creation, you will be automatically logged in as the owner of the organization, and the app will be shown in organization mode
32
+
7. After finishing the org creation, you will be automatically logged in as the owner of the organization, and the app will be shown in organization mode
33
33
34
34
### Note
35
35
36
36
Browsers do not allow camera/mic access on any non-HTTPS hosts except for localhost. To test cal video organization meeting links locally (`app.cal.local/video/[uid]`). You can access the meeting link by replacing app.cal.local with localhost in the URL.
37
37
38
-
For eg:- Use `http://localhost:3000/video/nAjnkjejuzis99NhN72rGt` instead of`http://app.cal.local:3000/video/nAjnkjejuzis99NhN72rGt`.
38
+
For eg:- Use `http://localhost:3000/video/nAjnkjejuzis99NhN72rGt` instead of `http://app.cal.local:3000/video/nAjnkjejuzis99NhN72rGt`.
39
39
40
40
To get an HTTPS URL for localhost, you can use a tunneling tool such as `ngrok` or [Tunnelmole](https://github.com/robbie-cahill/tunnelmole-client) . Alternatively, you can generate an SSL certificate for your local domain using `mkcert`. Turn off any SSL certificate validation in your HTTPS client (be sure to do this for local only, otherwise its a security risk).
@@ -59,15 +59,14 @@ View the Tunnelmole [README](https://github.com/robbie-cahill/tunnelmole-client)
59
59
60
60
#### ngrok - Closed Source Tunnelling Tool:
61
61
62
-
ngrok is a popular closed source tunneling tool. You can run ngrok using the same port, using the format `ngrok http <port>` replacing `<port>` with your actual port number. For example:
62
+
ngrok is a popular closed source tunneling tool. You can run ngrok using the same port, using the format `ngrok http <port>` replacing `<port>` with your actual port number. For example:
63
63
64
64
```
65
65
ngrok http 8000
66
66
```
67
67
68
68
This will generate a public URL that you can use to access your localhost server.
69
69
70
-
71
70
## DNS setup
72
71
73
72
When a new organization is created, other than not being verified up until the admin accepts it in settings as explained in step 6, a flag gets created that marks the organization as missing DNS setup. That flag get auto-checked by the system upon organization creation when the Cal instance is deployed in Vercel and the subdomain registration was successful. Logging in as admin and going to Settings > Organizations section, you will see that flag as a badge, designed to give admins a glimpe on what is pending in terms of making an organization work. Alongside the mentioned badge, an email gets sent to admins in order to warn them there is a pending action about setting up DNS for the newly created organization to work.
0 commit comments