chore: merged latest branch

CHANGELOG.md

@@ -3,6 +3,38 @@ All notable changes to this project will be documented in this file. See [conven
 
 - - -
 
+## 1.16.0 (2023-12-26)
+
+### Features
+
+- README.md PR title changes ([#134](https://github.com/juspay/hyperswitch-control-center/pull/134)) ([`66ef342`](https://github.com/juspay/hyperswitch-control-center/commit/66ef342d46095bac4a2901daac198b60d647d2c6))
+
+### Bug Fixes
+
+- FixedPageWidth Changes ([#132](https://github.com/juspay/hyperswitch-control-center/pull/132)) ([`921eab4`](https://github.com/juspay/hyperswitch-control-center/commit/921eab4629e0a921b6f29bc286a9009173180570))
+- APIUtils changes ([#135](https://github.com/juspay/hyperswitch-control-center/pull/135)) ([`9ec16e8`](https://github.com/juspay/hyperswitch-control-center/commit/9ec16e87f32e7564d363f6bbc9d0c323e816aa4f))
+- API fix and radio icon changes ([#136](https://github.com/juspay/hyperswitch-control-center/pull/136)) ([`2ee3bf2`](https://github.com/juspay/hyperswitch-control-center/commit/2ee3bf2f7fb10491ffe036a30c009da853e62366))
+
+### Refactors
+
+- ApiUtils file to use the apiPrefix once only ([#122](https://github.com/juspay/hyperswitch-control-center/pull/122)) ([`dc4e644`](https://github.com/juspay/hyperswitch-control-center/commit/dc4e644a9a7825bf74d47c5d225c71efb5b31369))
+
+**Full Changelog:** [`v1.15.1...v1.16.0`](https://github.com/juspay/hyperswitch-control-center/compare/v1.15.1...v1.16.0)
+
+- - -
+
+
+## 1.14.0 (2023-12-24)
+
+### Features
+
+- Sidebar expansion close ([#126](https://github.com/juspay/hyperswitch-control-center/pull/126)) ([`ea91fba`](https://github.com/juspay/hyperswitch-control-center/commit/ea91fba4505fc8b64e0bc161ca41d1395fb83af2))
+
+**Full Changelog:** [`v1.13.1...v1.14.0`](https://github.com/juspay/hyperswitch-control-center/compare/v1.13.1...v1.14.0)
+
+- - -
+
+
 ## 1.13.1 (2023-12-21)
 
 ### Bug Fixes

README.md

@@ -303,9 +303,10 @@ All commits should be signed to verify the authenticity of contributors. Follow
 
     ```bash
       gpg --armor --export <GPG_KEY_ID>
-      Replace <GPG_KEY_ID> with the actual key ID.
     ```
 
+    Replace <GPG_KEY_ID> with the actual key ID.
+
     b. Copy the entire output, including the lines that start with "-----BEGIN PGP PUBLIC KEY BLOCK-----" and "-----END PGP PUBLIC KEY BLOCK-----".
 
     c. Go to your GitHub Settings.
@@ -341,6 +342,57 @@ For further assistance, please refer to the [GitHub documentation on signing com
 
 ---
 
+## Standard Process for Raising a Pull Request (PR) from a Branch
+
+### Introduction
+
+Welcome to the standard process for raising a Pull Request (PR) directly from a branch in our project! Please follow these guidelines to ensure that your contributions align with our project's goals and standards.
+
+### Steps to Raise a PR from a Branch
+
+1. **Clone the Repository**:
+
+   - Clone the main repository to your local machine using the following command:
+     ```bash
+     git clone https://github.com/juspay/hyperswitch-control-center.git
+     ```
+
+2. **Create a New Branch**:
+
+   - Create a new branch for your changes directly in the main repository. Please ensure the branch name is descriptive and relates to the feature or bug you're addressing.
+     ```bash
+     git checkout -b feature/your-feature-name
+     ```
+
+3. **Make Changes**:
+
+   - Make the necessary changes in the codebase, ensuring that you follow the project's coding guidelines and standards.
+
+4. **Commit Changes**:
+
+   - Commit your changes with a clear and descriptive commit message. Please follow conventional commit [guidelines](https://www.conventionalcommits.org/).
+
+5. **Push Changes**:
+
+   - Push your changes to the branch in the main repository.
+     ```bash
+     git push origin feature/your-feature-name
+     ```
+
+6. **Create a Pull Request**:
+
+   - Navigate to the main repository on GitHub and create a new PR from your branch. Provide a detailed description of the changes, along with any relevant context or screenshots.
+
+7. **Respond to Feedback**:
+
+   - Be responsive to feedback from reviewers. Address any comments or suggestions promptly and make the necessary changes as required.
+
+### Additional Notes
+
+- Ensure your PR adheres to our coding guidelines, style conventions, and documentation standards.
+- Include relevant tests, documentation updates, or screenshots, if applicable.
+- Collaborate and communicate effectively with other contributors and maintainers throughout the review process.
+
 ## License
 
 This project is open-source and available under the MIT License.

cypress/e2e/auth/auth.cy.js

@@ -0,0 +1,24 @@
+describe("auth ui checks", () => {
+  beforeEach(() => {
+    cy.visit("http://localhost:9000/");
+  });
+
+  it("check the components in the login page", () => {
+    cy.url().should("include", "/login");
+    cy.get("#card-header").should("contain", "Hey there, Welcome back!");
+    cy.get("#card-subtitle").should("contain", "Sign up");
+    cy.get("#auth-submit-btn").should("exist");
+    cy.get("#tc-text").should("exist");
+    cy.get("#footer").should("exist");
+  });
+
+  it("check the components in the sign up page", () => {
+    cy.get("#card-subtitle").click();
+    cy.url().should("include", "/register");
+    cy.get("#card-header").should("contain", "Welcome to Hyperswitch");
+    cy.get("#card-subtitle").should("contain", "Sign in");
+    cy.get("#auth-submit-btn").should("exist");
+    cy.get("#tc-text").should("exist");
+    cy.get("#footer").should("exist");
+  });
+});