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

Fix typos and some redundancy #654

Merged
merged 7 commits into from
Apr 14, 2022
Merged

Conversation

yuktea
Copy link
Contributor

@yuktea yuktea commented Apr 2, 2022

Fixed a few typos and removed mentions of "from your bash compatible shell" (we use make so these commands are compatible with all clis).
A part of [Issue #481]

Fixed a few typos and removed mentions of "from your bash compatible
shell" (we use make so these commands are compatible with all clis)
@codecov
Copy link

codecov bot commented Apr 2, 2022

Codecov Report

Merging #654 (b7e7324) into main (99fba0d) will decrease coverage by 0.00%.
The diff coverage is n/a.

❗ Current head b7e7324 differs from pull request most recent head 5931cd4. Consider uploading reports for the commit 5931cd4 to get more accurate results

Impacted file tree graph

@@             Coverage Diff              @@
##               main     #654      +/-   ##
============================================
- Coverage     84.27%   84.27%   -0.01%     
+ Complexity     1152     1146       -6     
============================================
  Files           127      127              
  Lines          2786     2772      -14     
============================================
- Hits           2348     2336      -12     
+ Misses          438      436       -2     
Flag Coverage Δ
7.4 84.21% <ø> (-0.01%) ⬇️
8.0 84.27% <ø> (-0.01%) ⬇️
8.1 84.27% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
src/SDK/Common/Dev/Compatibility/Util.php 100.00% <0.00%> (+7.40%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 99fba0d...5931cd4. Read the comment docs.

README.md Outdated Show resolved Hide resolved
Co-authored-by: Brett McBride <brett.a.mcbride@gmail.com>
README.md Outdated

```bash
make all
```
Note: Copying `.env.dist` to `.env` fixes the warning ```The "PHP_USER" variable is not set. Defaulting to a blank string.```
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is really a necessary setup step - can we move it somewhere prominent? I think the very first step after git clone?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, @brettmc, I agree. I wanted to do that but was slightly hesitant. I think it'll be placed better after the git clone

README.md Outdated Show resolved Hide resolved
README.md Outdated
@@ -142,15 +144,16 @@ In order to update all the vendored libraries in the `/vendor` directory.

Once you've made the update to the codebase that you'd like to submit, you may [create a pull request](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request) to the opentelemetry-php project.
Copy link
Member

@tidal tidal Apr 5, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you please also reduce the visual noise of this? eg.:
"If you want to submit changes to the codebase, please create a pull request."

README.md Outdated

You can simulate the important github actions locally before you submit your PR by running the following command:
You can simulate the important GitHub actions locally before you submit your PR by running the following command:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I still feel this is wrong. This is not simulating GitHub actions, but is simply using the same commands as the CI.

README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated

You can use the [examples/AlwaysOnNewrelicExample.php](/examples/AlwaysOnNewrelicExample.php) file to test out the reference implementation we have for Newrelic. This example perfoms a sample trace with spans and POSTs the result to a Newrelic endpoint. This requires a license key (free accounts available) set in the environment (NEW_RELIC_INSERT_KEY) to authenticate to the backend.
You can use the [examples/AlwaysOnNewrelicExample.php](/examples/AlwaysOnNewrelicExample.php) file to test out the reference implementation we have for Newrelic. This example performs a sample trace with spans and POSTs the result to a Newrelic endpoint. This requires a license key (free accounts available) set in the environment (NEW_RELIC_INSERT_KEY) to authenticate to the backend.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you please remove both NewRelic examples. This is not an advertisment platform for NewRelic, and the associated exporters may be moved to the contrib repo anyway.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you please remove both NewRelic examples. This is not an advertisment platform for NewRelic, and the associated exporters may be moved to the contrib repo anyway.

@tidal , Is there a specific reason why we are choosing to remove the NewRelic examples

README.md Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
@tidal
Copy link
Member

tidal commented Apr 5, 2022

@yuktea
Thanks for your work.
I have added some comments, with things you could also fix while you are add it.
However this already looks much better.

@yuktea
Copy link
Contributor Author

yuktea commented Apr 5, 2022

@yuktea Thanks for your work. I have added some comments, with things you could also fix while you are add it. However, this already looks much better.

@tidal I will make these changes, I have a clearer understanding of how this needs to be with the comments. Thank you for reviewing the PR

@yuktea yuktea marked this pull request as draft April 14, 2022 08:59
@yuktea yuktea marked this pull request as ready for review April 14, 2022 09:06
@brettmc brettmc merged commit c242c37 into open-telemetry:main Apr 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants