Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New-feature-branch : Successfully pushed the full AES-256 and PBKDF2 encryption enhancements #148

Closed
wants to merge 8 commits into from

Conversation

Ishratnoori
Copy link

Hi @jindalpriyanshu101 and @jinx-vi-0,

I have successfully pushed the full AES-256 and PBKDF2 encryption enhancements in the new-feature-branch. You can find the changes in the pull request I created.

Thank you for your guidance throughout this process!

Best regards,
Ishrat noori :)

@jindalpriyanshu101
Copy link
Contributor

Well, looks like things are messed up as you kight have synced the fork before raising this PR.

I can see 517 file changes, and its next to impossible to find your actual changes in such case..

I'd recommend you to delete this branch, and redo your changes in a new up-to-dated branch. This way you'll not face any merge conflicts and it'll be easy for us to review your changes @Ishratnoori.

I appreciate your active cooperation till now ;D

@Ishratnoori
Copy link
Author

Ishratnoori commented Nov 5, 2024

image
Can i create a pull request?
its displaying like CANT AUTOMATICALLY MERGE
what should i do?

@Ishratnoori
Copy link
Author

image

@jindalpriyanshu101
Copy link
Contributor

image
Can i create a pull request?
its displaying like CANT AUTOMATICALLY MERGE
what should i do?

Yup, you should be creating a pull request only.

@jindalpriyanshu101 jindalpriyanshu101 added the invalid This doesn't seem right label Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants