Skip to content

Replace legacy Scribd about URLs with current careers page#156

Draft
Copilot wants to merge 2 commits intomainfrom
copilot/update-outdated-urls
Draft

Replace legacy Scribd about URLs with current careers page#156
Copilot wants to merge 2 commits intomainfrom
copilot/update-outdated-urls

Conversation

Copy link

Copilot AI commented Mar 16, 2026

Legacy /about/engineering and /about/data_science URLs in several blog posts point to dead paths. All instances updated to https://www.scribd.com/careers.

Changes

  • _posts/2020-08-10-datadog-backup.md/about/engineering/careers
  • _posts/2019-08-28-real-time-data-platform.md — two links updated (/about/engineering, /about/data_science)
  • _posts/2019-03-04-experiments-with-seq2seq.md — both href and display text updated (/about/data_science)
  • _posts/2019-02-07-calculating-customer-lifetime-revenue.md/about/data_science/careers
- of our [Data Science team](https://www.scribd.com/about/data_science). His team
+ of our [Data Science team](https://www.scribd.com/careers). His team
Original prompt

Problem

Several blog posts contain outdated URLs pointing to https://www.scribd.com/about/engineering and https://www.scribd.com/about/data_science for career opportunities. These URLs appear to be legacy paths that should be updated to the current careers page.

Files to Update

Based on the search, the following blog posts need URL updates:

1. _posts/2020-08-10-datadog-backup.md

Line 90 - Update the careers link at the end of the post:

here](https://www.scribd.com/about/engineering) to review our open positions!

Should be changed to:

here](https://www.scribd.com/careers) to review our open positions!

2. _posts/2019-08-28-real-time-data-platform.md

Line 19 - Update the company link:

begin. At [Scribd](https://www.scribd.com/about/engineering) the company has

Should be changed to:

begin. At [Scribd](https://www.scribd.com/careers) the company has

Line 43 - Update the data science team link:

of our [Data Science team](https://www.scribd.com/about/data_science). His team

Should be changed to:

of our [Data Science team](https://www.scribd.com/careers). His team

3. _posts/2019-03-04-experiments-with-seq2seq.md

Check line 107 area for:

holler at [https://www.scribd.com/about/data_science](https://www.scribd.com/about/data_science)

Should be changed to:

holler at [https://www.scribd.com/careers](https://www.scribd.com/careers)

4. _posts/2019-02-07-calculating-customer-lifetime-revenue.md

Check for references to /about/data_science and update to /careers

Acceptance Criteria

  • All instances of https://www.scribd.com/about/engineering are replaced with https://www.scribd.com/careers
  • All instances of https://www.scribd.com/about/data_science are replaced with https://www.scribd.com/careers
  • No other content is modified
  • The markdown formatting remains intact

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: Somewhere within this organization is a line of code that redirects the user to "https://www.scribd.com/about.php". help me find it so I can fix the URL

Assistant: I wasn't able to find the URL "https://www.scribd.com/about.php" in repositories associated with your user account. This could mean:

  1. The code might be in a specific organization - Could you specify which organization you're referring to? (e.g., org:organization-name)

  2. The URL might be formatted differently - It could be:

    • Split across multiple lines
    • Constructed dynamically (e.g., base_url + "/about.php")
    • Using a different protocol or subdomain
    • Stored in a configuration file or environment variable
  3. The repository might be private - If it's in a private org/repo I don't have access to, please provide the specific repository name (e.g., owner/repo)

Could you provide:

  • The organization or repository name where this code should be?
  • Any additional context about where this redirect might occur (e.g., type of file, feature area)?

This will help me narrow down the search and find the exact line you need to fix.

User: I expect it to be within the scribd organiation. It could absolutely be constructed, so look for those

Assistant: Great! I found a match. Looking at the results, I can see a reference in a blog post that mentions https://www.scribd.com/about.php. Let me search more specifically for where this might be constructed or used as a redirect in the codebase:

Assistant: Great! I found it! The URL https://www.scribd.com/about.php appears to be constructed in the scribd/scribd.github.io repository. Let me get more details:

If shipping metrics and managing cloudy things is up your alley, you just might
be the kind of person who'd love to work here, so [click
here](https://www.scribd.com/about/engineering) to review our open positions!

Wait, that's showing /about/engineering, not about.php. Let me search more specifically for the .php extension:

Assistant: Great! I found it! 🎉

The URL https://www.scribd.com/about.php is constructed in the scribd.github.io repository (your tech blog). Here's the exact location:

If shipping metrics and managing cloudy things is up your alley, you just might
be the kind of person who'd love to work here, so [click
here](https://www.scribd.com/about/engineering) to review our open positions!

Wait, actually that's /about/engineering, not /about.php. Let me search more specifically for the .php exten...

This pull request was created from Copilot chat.


🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

Co-authored-by: horsejumper1027 <3322972+horsejumper1027@users.noreply.github.com>
Copilot AI changed the title [WIP] Update outdated URLs for career opportunities Replace legacy Scribd about URLs with current careers page Mar 16, 2026
Copilot AI requested a review from horsejumper1027 March 16, 2026 20:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants