-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
Update information #166
Open
Puneetsingh25
wants to merge
1
commit into
pkic:main
Choose a base branch
from
Puneetsingh25:patch-5
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Update information #166
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@Puneetsingh25 why do you keep creating a new pull request instead of updating a currently open pull request? Who should be listed as representative? The PR removes the representative and would not list anyone. |
@***@***.***> : Can you please look into it?
Thank you,
Puneet Singh
Principal
Encryption Consulting LLC
email: ***@***.******@***.***>
Tel: +1 469 815 4136
Cell: +1 469 400 7592
130 N Preston Rd, Prosper TX 75078
From: Sven ***@***.***>
Sent: Tuesday, July 23, 2024 10:55 AM
To: pkic/pkic.org ***@***.***>
Cc: Puneet ***@***.***>; Mention ***@***.***>
Subject: Re: [pkic/pkic.org] Update information (PR #166)
@Puneetsingh25<https://github.com/Puneetsingh25> why do you keep creating a new pull request instead of updating a currently open pull request? Who should be listed as representative? The PR removes the representative and would not list anyone.
-
Reply to this email directly, view it on GitHub<#166 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANTM7V4H2PSEBU3RS5YWJXTZNZ4FLAVCNFSM6AAAAABLKW6KOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBVGYZDMOJVGI>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
Hello Team,
Sorry for creating a new pull request. The pull request I made isn't updating with the new information, it shows 'Merging is blocked. The base branch restricts merging to authorized users.' How can I overcome this issue? How do I update the information in https://github.com/pkic/pkic.org/blob/main/data/members/encryptionconsulting.yaml? Could you please provide a solution? I have also attached a screenshot for reference.
***@***.***
Thank you,
Nischinth
Consultant
Encryption Consulting LLC
email: ***@***.******@***.***>
Tel: +1 469 815 4136
130 N Preston Rd, Prosper TX 75078
www.encryptionconsulting.com<http://www.encryptionconsulting.com/>
From: Puneet ***@***.***>
Sent: Tuesday, July 23, 2024 9:33 PM
To: pkic/pkic.org ***@***.***>; pkic/pkic.org ***@***.***>; Nischinth ***@***.***>
Cc: Mention ***@***.***>
Subject: RE: [pkic/pkic.org] Update information (PR #166)
@***@***.***> : Can you please look into it?
Thank you,
Puneet Singh
Principal
Encryption Consulting LLC
email: ***@***.******@***.***>
Tel: +1 469 815 4136
Cell: +1 469 400 7592
130 N Preston Rd, Prosper TX 75078
From: Sven ***@***.******@***.***>>
Sent: Tuesday, July 23, 2024 10:55 AM
To: pkic/pkic.org ***@***.******@***.***>>
Cc: Puneet ***@***.******@***.***>>; Mention ***@***.******@***.***>>
Subject: Re: [pkic/pkic.org] Update information (PR #166)
@Puneetsingh25<https://github.com/Puneetsingh25> why do you keep creating a new pull request instead of updating a currently open pull request? Who should be listed as representative? The PR removes the representative and would not list anyone.
-
Reply to this email directly, view it on GitHub<#166 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANTM7V4H2PSEBU3RS5YWJXTZNZ4FLAVCNFSM6AAAAABLKW6KOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBVGYZDMOJVGI>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
Hello All-
Any update on the below request? How can we update our information?
Thank you,
Puneet Singh
Principal
Encryption Consulting LLC
email: ***@***.******@***.***>
Tel: +1 469 815 4136
Cell: +1 469 400 7592
130 N Preston Rd, Prosper TX 75078
From: Nischinth ***@***.***>
Sent: Tuesday, July 23, 2024 11:14 AM
To: pkic/pkic.org ***@***.***>; pkic/pkic.org ***@***.***>
Cc: Mention ***@***.***>; Puneet ***@***.***>
Subject: RE: [pkic/pkic.org] Update information (PR #166)
Hello Team,
Sorry for creating a new pull request. The pull request I made isn't updating with the new information, it shows 'Merging is blocked. The base branch restricts merging to authorized users.' How can I overcome this issue? How do I update the information in https://github.com/pkic/pkic.org/blob/main/data/members/encryptionconsulting.yaml? Could you please provide a solution? I have also attached a screenshot for reference.
***@***.***
Thank you,
Nischinth
Consultant
Encryption Consulting LLC
email: ***@***.******@***.***>
Tel: +1 469 815 4136
130 N Preston Rd, Prosper TX 75078
www.encryptionconsulting.com<http://www.encryptionconsulting.com/>
From: Puneet ***@***.******@***.***>>
Sent: Tuesday, July 23, 2024 9:33 PM
To: pkic/pkic.org ***@***.******@***.***>>; pkic/pkic.org ***@***.******@***.***>>; Nischinth ***@***.******@***.***>>
Cc: Mention ***@***.******@***.***>>
Subject: RE: [pkic/pkic.org] Update information (PR #166)
@***@***.***> : Can you please look into it?
Thank you,
Puneet Singh
Principal
Encryption Consulting LLC
email: ***@***.******@***.***>
Tel: +1 469 815 4136
Cell: +1 469 400 7592
130 N Preston Rd, Prosper TX 75078
From: Sven ***@***.******@***.***>>
Sent: Tuesday, July 23, 2024 10:55 AM
To: pkic/pkic.org ***@***.******@***.***>>
Cc: Puneet ***@***.******@***.***>>; Mention ***@***.******@***.***>>
Subject: Re: [pkic/pkic.org] Update information (PR #166)
@Puneetsingh25<https://github.com/Puneetsingh25> why do you keep creating a new pull request instead of updating a currently open pull request? Who should be listed as representative? The PR removes the representative and would not list anyone.
-
Reply to this email directly, view it on GitHub<#166 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANTM7V4H2PSEBU3RS5YWJXTZNZ4FLAVCNFSM6AAAAABLKW6KOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBVGYZDMOJVGI>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
The changes are reviewed and then approved by Paul or I. Who should be listed as representative since the PR removes you? Do you want no one listed as a representative for Encryption Consulting? |
Right now you can remove me from there and we are right making decision on rebuilding leadership team. When we have a decision we will update again.
Thank you,
Puneet Singh
Principal
Encryption Consulting LLC
email: ***@***.******@***.***>
Tel: +1 469 815 4136
Cell: +1 469 400 7592
130 N Preston Rd, Prosper TX 75078
From: Sven ***@***.***>
Sent: Thursday, July 25, 2024 3:36 PM
To: pkic/pkic.org ***@***.***>
Cc: Puneet ***@***.***>; Mention ***@***.***>
Subject: Re: [pkic/pkic.org] Update information (PR #166)
The changes are reviewed and then approved by Paul or I. Who should be listed as representative since the PR removes you? Do you want no one listed as a representative for Encryption Consulting?
-
Reply to this email directly, view it on GitHub<#166 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANTM7VZJ2YBRNJ2FTXU46UDZOFOURAVCNFSM6AAAAABLKW6KOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJRGM2TAOJSGQ>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.