Improve utm_source in README.md
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 66
- Forks
- 36
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
Is your feature request related to a problem?
Our README.md contains a link with a utm_source that is set to wordpress.org. However, this information is incorrect if the link gets clicked from within GitHub for example.
Describe the solution you'd like
Default the utm_source to github.com, and update it to wordpress.org during the release automated workflow. This way, links will be correct in both the wp-parsely repo and https://wordpress.org/plugins/wp-parsely/.
Additional context
Proposed here by @GaryJones.
Could make this
utm_sourcedynamic - have it say github.com by default, but just before it's pushed to WPORG, do a replacement to make it say wordpress.org.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with README.md to find the link whose utm_source is wordpress.org, then locate the release automated workflow that publishes to WordPress.org. Set the repository link to github.com and have the release process replace it with wordpress.org before publication; verify both README and release output contain the intended source.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, wordpress
- Domain
- documentation, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100