Rocket.Chat

Commit Graph

Author	SHA1	Message	Date
Kevin Aleman	eb3ad21fd7	chore: Disable caching for ms command (#39581 )	2 months ago
Rodrigo Nascimento	06915142d2	chore(ci): do not include dev dependencies in docker images (#37481 )	6 months ago
Rodrigo Nascimento	4085cf7e7f	chore(ci): reduce number of parallel jobs and improve container builds (#37466 )	6 months ago
Rodrigo Nascimento	e54fd03984	chore(CI): improve workflow merging steps and parallelizing image build (#37352 ) Co-authored-by: Guilherme Gazzo <guilherme@gazzo.xyz>	6 months ago
Matheus Cardoso	2cc7cc5166	chore: move tsconfig bases from root to a package (#35987 ) Co-authored-by: Guilherme Gazzo <guilherme@gazzo.xyz> Co-authored-by: Pierre Lehnen <55164754+pierre-lehnen-rc@users.noreply.github.com>	11 months ago
gabriellsh	aadc7956bd	feat: Draggable Voice/Video call popup (#35830 ) Co-authored-by: Tasso Evangelista <2263066+tassoevan@users.noreply.github.com>	12 months ago
Guilherme Gazzo	f22a6db120	test: bring back coverage e2e (#35803 )	1 year ago
Guilherme Gazzo	c5f23abd01	chore: bump meteor and node version (#34048 ) Co-authored-by: Diego Sampaio <chinello@gmail.com> Co-authored-by: Marcos Spessatto Defendi <marcos.defendi@rocket.chat>	1 year ago
Guilherme Gazzo	9ef096fd9c	chore: publish preview github pages (#33248 )	2 years ago
Guilherme Gazzo	93f99ddcab	chore: bump turbo (#32938 )	2 years ago
Guilherme Gazzo	9457442c0a	chore(ddp-streamer): fix cache problem from importing files from another package (#32190 )	2 years ago
Guilherme Gazzo	b5171a2b29	chore: cache ui-context package (#31805 )	2 years ago
Guilherme Gazzo	5ff4110886	ci: change arg place to reuse cache (#31800 )	2 years ago
Guilherme Gazzo	6fd370fde8	chore: streams refactor (#29585 )	3 years ago
Guilherme Gazzo	29b78ee655	ci: Report Jest coverage (#29848 )	3 years ago
Guilherme Gazzo	ee75fc2e82	chore: bump turbo (#29696 )	3 years ago
Guilherme Gazzo	fd3532d4f5	refactor: create i18n package (#29097 ) Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com> Co-authored-by: Marcos Spessatto Defendi <marcos.defendi@rocket.chat>	3 years ago
Dongwoo Gim	574d381488	chore: Remove duplicated key in turbo.json (#29057 ) Co-authored-by: Tasso Evangelista <tasso.evangelista@rocket.chat>	3 years ago
Rodrigo Nascimento	f17ded54b3	Chore: Improve time of meteor build (#28128 )	3 years ago
Diego Sampaio	6d3b20d81c	Chore: Move presence to package (#25541 )	4 years ago
Tasso Evangelista	6953c06dc4	[NEW] `Home` page (#25734 ) Co-authored-by: gabriellsh <40830821+gabriellsh@users.noreply.github.com> Co-authored-by: Luciano Marcos Pierdona Junior <64279791+LucianoPierdona@users.noreply.github.com> Co-authored-by: Guilherme Jun Grillo <48109548+guijun13@users.noreply.github.com> Co-authored-by: Hugo Costa <20212776+hugocostadev@users.noreply.github.com>	4 years ago
Tasso Evangelista	5f5b228ed5	Chore: Bypass turbo cache on `ui-contexts` (#26526 )	4 years ago
Filipe Marins	4c82605269	Regression: remove italic from reaction translation (#26152 )	4 years ago
Guilherme Gazzo	3544ed0a73	Chore: Revert `yarn dev` implementation (#26075 )	4 years ago
gabriellsh	016584b599	[FIX] Too many watchers in dev environment. (#25930 ) <!-- This is a pull request template, you do not need to uncomment or remove the comments, they won't show up in the PR text. --> <!-- Your Pull Request name should start with one of the following tags [NEW] For new features [IMPROVE] For an improvement (performance or little improvements) in existing features [FIX] For bug fixes that affect the end-user [BREAK] For pull requests including breaking changes Chore: For small tasks Doc: For documentation --> <!-- Checklist!!! If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. - I have read the Contributing Guide - https://github.com/RocketChat/Rocket.Chat/blob/develop/.github/CONTRIBUTING.md#contributing-to-rocketchat doc - I have signed the CLA - https://cla-assistant.io/RocketChat/Rocket.Chat - Lint and unit tests pass locally with my changes - I have added tests that prove my fix is effective or that my feature works (if applicable) - I have added necessary documentation (if applicable) - Any dependent changes have been merged and published in downstream modules --> ## Proposed changes (including videos or screenshots) <!-- CHANGELOG --> <!-- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue below. This description will appear in the release notes if we accept the contribution. --> <!-- END CHANGELOG --> ## Issue(s) <!-- Link the issues being closed by or related to this PR. For example, you can use #594 if this PR closes issue number 594 --> ## Steps to test or reproduce <!-- Mention how you would reproduce the bug if not mentioned on the issue page already. Also mention which screens are going to have the changes if applicable --> ## Further comments <!-- If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc... -->	4 years ago
Júlia Jaeger Foresti	d0f8643f01	[FIX] sidebar colors (#25987 ) <!-- This is a pull request template, you do not need to uncomment or remove the comments, they won't show up in the PR text. --> <!-- Your Pull Request name should start with one of the following tags [NEW] For new features [IMPROVE] For an improvement (performance or little improvements) in existing features [FIX] For bug fixes that affect the end-user [BREAK] For pull requests including breaking changes Chore: For small tasks Doc: For documentation --> <!-- Checklist!!! If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. - I have read the Contributing Guide - https://github.com/RocketChat/Rocket.Chat/blob/develop/.github/CONTRIBUTING.md#contributing-to-rocketchat doc - I have signed the CLA - https://cla-assistant.io/RocketChat/Rocket.Chat - Lint and unit tests pass locally with my changes - I have added tests that prove my fix is effective or that my feature works (if applicable) - I have added necessary documentation (if applicable) - Any dependent changes have been merged and published in downstream modules --> ## Proposed changes (including videos or screenshots) <!-- CHANGELOG --> <!-- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue below. This description will appear in the release notes if we accept the contribution. --> <!-- END CHANGELOG --> ## Issue(s) <!-- Link the issues being closed by or related to this PR. For example, you can use #594 if this PR closes issue number 594 --> ## Steps to test or reproduce <!-- Mention how you would reproduce the bug if not mentioned on the issue page already. Also mention which screens are going to have the changes if applicable --> ## Further comments <!-- If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc... --> Co-authored-by: Guilherme Gazzo <5263975+ggazzo@users.noreply.github.com>	4 years ago
Guilherme Gazzo	b0b1a0ca0a	Regression: Fix e2e CI (#25974 )	4 years ago
Pierre Lehnen	d0078fefab	Chore: Keep the option to run only the meteor app (#25915 ) <!-- This is a pull request template, you do not need to uncomment or remove the comments, they won't show up in the PR text. --> <!-- Your Pull Request name should start with one of the following tags [NEW] For new features [IMPROVE] For an improvement (performance or little improvements) in existing features [FIX] For bug fixes that affect the end-user [BREAK] For pull requests including breaking changes Chore: For small tasks Doc: For documentation --> <!-- Checklist!!! If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. - I have read the Contributing Guide - https://github.com/RocketChat/Rocket.Chat/blob/develop/.github/CONTRIBUTING.md#contributing-to-rocketchat doc - I have signed the CLA - https://cla-assistant.io/RocketChat/Rocket.Chat - Lint and unit tests pass locally with my changes - I have added tests that prove my fix is effective or that my feature works (if applicable) - I have added necessary documentation (if applicable) - Any dependent changes have been merged and published in downstream modules --> ## Proposed changes (including videos or screenshots) <!-- CHANGELOG --> <!-- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue below. This description will appear in the release notes if we accept the contribution. --> <!-- END CHANGELOG --> ## Issue(s) <!-- Link the issues being closed by or related to this PR. For example, you can use #594 if this PR closes issue number 594 --> ## Steps to test or reproduce <!-- Mention how you would reproduce the bug if not mentioned on the issue page already. Also mention which screens are going to have the changes if applicable --> ## Further comments <!-- If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc... -->	4 years ago
gabriellsh	06043f52cc	Chore: Watch for package changes (#25910 ) <!-- This is a pull request template, you do not need to uncomment or remove the comments, they won't show up in the PR text. --> <!-- Your Pull Request name should start with one of the following tags [NEW] For new features [IMPROVE] For an improvement (performance or little improvements) in existing features [FIX] For bug fixes that affect the end-user [BREAK] For pull requests including breaking changes Chore: For small tasks Doc: For documentation --> <!-- Checklist!!! If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. - I have read the Contributing Guide - https://github.com/RocketChat/Rocket.Chat/blob/develop/.github/CONTRIBUTING.md#contributing-to-rocketchat doc - I have signed the CLA - https://cla-assistant.io/RocketChat/Rocket.Chat - Lint and unit tests pass locally with my changes - I have added tests that prove my fix is effective or that my feature works (if applicable) - I have added necessary documentation (if applicable) - Any dependent changes have been merged and published in downstream modules --> ## Proposed changes (including videos or screenshots) <!-- CHANGELOG --> <!-- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue below. This description will appear in the release notes if we accept the contribution. --> With the current `dev` pipeline, whenever we modify a package (e.g. `api-client`), we have to kill the meteor proccess and run `yarn dev` again in order for the changes to be compiled and the new output to be used by meteor. This has the drawback of taking a little longer to run the dev environment, since we can't cache a watched buid. In the other hand, it reduces the friction of modifying internal packages since we don't need to rebuild the project for changes to take effect. This will enable us to move more things to separate packages without affecting the dev experience too much. <!-- END CHANGELOG --> ## Issue(s) <!-- Link the issues being closed by or related to this PR. For example, you can use #594 if this PR closes issue number 594 --> ## Steps to test or reproduce <!-- Mention how you would reproduce the bug if not mentioned on the issue page already. Also mention which screens are going to have the changes if applicable --> ## Further comments <!-- If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc... -->	4 years ago
Guilherme Gazzo	977f167faa	Chore: move definitions to packages (#25085 )	4 years ago
Guilherme Gazzo	19e90eff22	Regression: Fix CI monorepo build (#25107 )	4 years ago
Diego Sampaio	b30501c9dd	CI using monorepo	4 years ago
Diego Sampaio	961c06014e	First move to monorepo	4 years ago

33 Commits (a7b45d94deade86bbef8129db17d4b6945881241)