@Dash the application fee on our site is out of date, it should be $50. Fix it everywhere it appears.
Live in Slack or Microsoft Teams
Fix an outdated fee across a GitHub site
The application fee on the public site still reads $45 after a move to $50. Dash searches the whole repository rather than the page you would expect, finds every instance across three files, and stages the change for review before anything goes live.
Get started for free Chat with Dash, the AI teammate that works inside Slack and Microsoft Teams.
Found it in four places across three files, not the one page you would expect. Here is what I am about to change.
$45 → $50
- index.html: the fee line in the "How to apply" panel.
- vacancies.html: the fee note under the listing grid.
- faq.html: twice, once in "What does it cost to apply" and once in the deposits answer further down.
The second instance in faq.html is the one worth flagging. It is inside an answer about deposits, so it does not read as a fee line and a page by page check would step over it. I searched the repository for the value instead of the heading, which is how it turned up.
Staged on a branch for you to look at. Nothing is published.
👀 3
Four? I would have fixed the two obvious ones and left the FAQ wrong for another six months.
That is the usual outcome, and it is why I check the value rather than the page. Say the word and I will merge it.
Merge it.
Teams @Dash the application fee on our site is out of date, it should be $50. Fix it everywhere it appears.
Found it in four places across three files, not the one page you would expect. Here is what I am about to change.
$45 → $50
- index.html: the fee line in the "How to apply" panel.
- vacancies.html: the fee note under the listing grid.
- faq.html: twice, once in "What does it cost to apply" and once in the deposits answer further down.
The second instance in faq.html is the one worth flagging. It is inside an answer about deposits, so it does not read as a fee line and a page by page check would step over it. I searched the repository for the value instead of the heading, which is how it turned up.
Staged on a branch for you to look at. Nothing is published.
👀 3
Four? I would have fixed the two obvious ones and left the FAQ wrong for another six months.
That is the usual outcome, and it is why I check the value rather than the page. Say the word and I will merge it.
Merge it.