Skip to content

Conversation

@iranlegal
Copy link
Contributor

Add Iran Legal as a Go user in Iran with GitHub Go project link.

@google-cla
Copy link

google-cla bot commented Sep 7, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@gopherbot
Copy link

This PR (HEAD: 6b39464) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/wiki/+/701595.

Important tips:

  • Don't comment on this PR. All discussion takes place in Gerrit.
  • You need a Gmail or other Google account to log in to Gerrit.
  • To change your code in response to feedback:
    • Push a new commit to the branch used by your GitHub PR.
    • A new "patch set" will then appear in Gerrit.
    • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
    • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
    • Multiple commits in the PR will be squashed by GerritBot.
  • The title and description of the GitHub PR are used to construct the final commit message.
    • Edit these as needed via the GitHub web interface (not via Gerrit or git).
    • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
  • See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.
@gopherbot
Copy link

Message from Gopher Robot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
A maintainer will review your change and provide feedback. See
https://go.dev/doc/contribute#review for more info and tips to get your
patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.


Please don’t reply on this GitHub thread. Visit golang.org/cl/701595.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link

Message from Sean Liao:

Patch Set 1:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/701595.
After addressing review feedback, remember to publish your drafts!

Change-Id: I5672d50df7235f68bb2aa49ee27e313ad718447a
@gopherbot
Copy link

This PR (HEAD: f717fbf) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/wiki/+/701595.

Important tips:

  • Don't comment on this PR. All discussion takes place in Gerrit.
  • You need a Gmail or other Google account to log in to Gerrit.
  • To change your code in response to feedback:
    • Push a new commit to the branch used by your GitHub PR.
    • A new "patch set" will then appear in Gerrit.
    • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
    • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
    • Multiple commits in the PR will be squashed by GerritBot.
  • The title and description of the GitHub PR are used to construct the final commit message.
    • Edit these as needed via the GitHub web interface (not via Gerrit or git).
    • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
  • See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.
@gopherbot
Copy link

Message from Sasan Barkhordari:

Patch Set 1:

(2 comments)


Please don’t reply on this GitHub thread. Visit golang.org/cl/701595.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link

Message from Sean Liao:

Patch Set 2:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/701595.
After addressing review feedback, remember to publish your drafts!

@iranlegal iranlegal changed the title Add Iran Legal under Iran in GoUsers.md Sep 14, 2025
@gopherbot
Copy link

Message from iran legal:

Patch Set 2:

(2 comments)


Please don’t reply on this GitHub thread. Visit golang.org/cl/701595.
After addressing review feedback, remember to publish your drafts!

gopherbot pushed a commit that referenced this pull request Sep 14, 2025
Add Iran Legal as a Go user in Iran with GitHub Go project link.

Change-Id: I5672d50df7235f68bb2aa49ee27e313ad718447a
GitHub-Last-Rev: f717fbf
GitHub-Pull-Request: #68
Reviewed-on: https://go-review.googlesource.com/c/wiki/+/701595
Reviewed-by: Sean Liao <sean@liao.dev>
@gopherbot
Copy link

This PR is being closed because golang.org/cl/701595 has been merged.

@gopherbot gopherbot closed this Sep 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants