From b553e1835dd22d976cc8555418e51ad9cc8ae8e2 Mon Sep 17 00:00:00 2001 From: Isaack Mungui Date: Sat, 11 Mar 2023 14:52:04 +0300 Subject: [PATCH 1/3] replaced image path cloudinary url [Fixes #118] --- src/components/Events/Events.tsx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/components/Events/Events.tsx b/src/components/Events/Events.tsx index 68e4356..5c45e67 100644 --- a/src/components/Events/Events.tsx +++ b/src/components/Events/Events.tsx @@ -16,7 +16,7 @@ const events: EventData[] = [ title: 'Weekly Online Standups', description: 'Weekly open calls in the community’s Telegram group discussing industry-related topics.', - image_url: '/images/weekly_standups.jpg', + image_url: 'https://res.cloudinary.com/reactjs-devs-ke/image/upload/v1678532589/website-images/weekly_standups_lg3rth.jpg', target: 'https://bit.ly/joinreactdevske', }, { From 9f7873d76b7f2a0a240877632a6e237890b58fea Mon Sep 17 00:00:00 2001 From: Isaack Mungui Date: Sat, 11 Mar 2023 15:05:53 +0300 Subject: [PATCH 2/3] Added cloudinary to list of domains --- next.config.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/next.config.js b/next.config.js index 0163f2d..7dbba53 100644 --- a/next.config.js +++ b/next.config.js @@ -7,7 +7,7 @@ const nextConfig = { dirs: ['src', 'e2e'], }, images: { - domains: ['bit.ly'], + domains: ['bit.ly', 'res.cloudinary.com'], }, }; From b37fef1261b4fd4a5507e0265c4e22eef2d7104e Mon Sep 17 00:00:00 2001 From: Isaack Mungui Date: Sat, 11 Mar 2023 15:12:08 +0300 Subject: [PATCH 3/3] Modified contribution guidelines [Fixes #121] --- CONTRIBUTING.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 57e72b1..2df5033 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -101,16 +101,20 @@ npm run dev - Open this directory in your favorite text editor / IDE, and see your changes live by visiting `localhost:3000` from your browser - Pro Tip: Explore scripts within `package.json` for more build options -1. Commit and prepare for pull request (PR). In your PR commit message, reference the issue it resolves (see [how to link a commit message to an issue using a keyword](https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword). +1. Add changes made to the repo addressing an issue +``` +git add [file_name] +``` +2. Commit and prepare for pull request (PR). In your PR commit message, reference the issue it resolves (see [how to link a commit message to an issue using a keyword](https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword). ``` $ git commit -m "brief description of changes [Fixes #1234]" ``` -4. Push to your GitHub account +1. Push to your GitHub account ``` -$ git push +$ git push -u origin [feature_branch] ``` ### Submit your Pull Request (PR)🚀