Skip to content

Conversation

@ahmedNaser7
Copy link
Collaborator

@ahmedNaser7 ahmedNaser7 commented Nov 3, 2025

No description provided.

Pass `name` and `imageUrl` to the `DukanCard` component instead of the entire `dukan` object.
# Conflicts:
#	dukan_presentation/src/commonMain/composeResources/values-ar/strings.xml
# Conflicts:
#	dukan_presentation/src/commonMain/composeResources/values-ar/strings.xml
#	dukan_presentation/src/commonMain/composeResources/values/strings.xml
#	dukan_presentation/src/commonMain/kotlin/net/thechance/mena/dukan/presentation/screen/main/components/TopAppBar.kt
@ahmedNaser7 ahmedNaser7 self-assigned this Nov 3, 2025
@ahmedNaser7 ahmedNaser7 added the Dukan this PR belong to Dukan feature label Nov 3, 2025
@github-actions
Copy link

github-actions bot commented Nov 3, 2025

Invalid Branch Name: Feature/DKN-96-add-search-feature

Thank you for your contribution! However, the branch name does not follow our required naming convention.
This check must pass before the pull request can be merged.

Please rename your branch to match the following pattern:
<type>/<jira-key>-<short-description>


Pattern Breakdown:

  • type: One of feature, fix, refactor, test.
  • jira-key: One of IDN, DKN, CHT, FTH, TRN, WLT, followed by a hyphen and the issue number.
  • short-description: A short description of the change (e.g., add-user-login).

Examples of valid branch names:

  • feature/IDN-123-add-user-login
  • fix/TRN-45-update-payment-gateway

How to fix this:

  1. Go back to your local repository and rename the branch:
    git branch -m Feature/DKN-96-add-search-feature <new-branch-name>
    
  2. Push the renamed branch to the remote repository. You may need to use force push:
    git push origin -u <new-bottom-name> --force
    
  3. Please make a new PR with the updated branch.

@ahmedNaser7 ahmedNaser7 closed this Nov 3, 2025
@ahmedNaser7 ahmedNaser7 deleted the Feature/DKN-96-add-search-feature branch November 4, 2025 00:15
@github-actions
Copy link

github-actions bot commented Nov 4, 2025

Invalid Branch Name: Feature/DKN-96-add-search-feature

Thank you for your contribution! However, the branch name does not follow our required naming convention.
This check must pass before the pull request can be merged.

Please rename your branch to match the following pattern:
<type>/<jira-key>-<short-description>


Pattern Breakdown:

  • type: One of feature, fix, refactor, test.
  • jira-key: One of IDN, DKN, CHT, FTH, TRN, WLT, followed by a hyphen and the issue number.
  • short-description: A short description of the change (e.g., add-user-login).

Examples of valid branch names:

  • feature/IDN-123-add-user-login
  • fix/TRN-45-update-payment-gateway

How to fix this:

  1. Go back to your local repository and rename the branch:
    git branch -m Feature/DKN-96-add-search-feature <new-branch-name>
    
  2. Push the renamed branch to the remote repository. You may need to use force push:
    git push origin -u <new-bottom-name> --force
    
  3. Please make a new PR with the updated branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Dukan this PR belong to Dukan feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants