Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 20:53
    Managor opened #6601
  • 20:42
    CleanMachine1 commented #6595
  • 20:41
    invakid404 synchronize #6589
  • 08:25
    newtant opened #6600
  • 06:50
    einverne synchronize #6598
  • 06:36
    blueskyson edited #6599
  • 06:32
    blueskyson edited #6599
  • 06:31
    blueskyson labeled #6599
  • 06:31
    blueskyson opened #6599
  • 06:07

    github-actions[bot] on master

    [GitHub Actions] uploaded asset… (compare)

  • 06:06

    owenvoke on main

    [GitHub Actions] uploaded asset… (compare)

  • 06:06

    github-actions[bot] on master

    [GitHub Actions] uploaded asset… (compare)

  • 06:05

    owenvoke on main

    [GitHub Actions] uploaded asset… (compare)

  • 06:04

    github-actions[bot] on master

    debsecan: add page (#6567) (compare)

  • 06:04

    blueskyson on main

    debsecan: add page (#6567) (compare)

  • 06:04
    blueskyson closed #6567
  • 06:03

    github-actions[bot] on master

    sdk: (#6580) (compare)

  • 06:03

    blueskyson on main

    sdk: (#6580) (compare)

  • 06:03
    blueskyson closed #6580
  • 05:56

    github-actions[bot] on master

    [GitHub Actions] uploaded asset… (compare)

marchersimon
@marchersimon
Maybe it just needs some time
4 replies
Starbeamrainbowlabs
@sbrl
Got a link to those failing tests @marchersimon?
marchersimon
@marchersimon
That's one: https://github.com/tldr-pages/tldr/runs/3509653805?check_suite_focus=true
CleanMachine1
@CleanMachine1
Can I get a force merge here tldr-pages/tldr#6470 ?
marchersimon
@marchersimon
image
CleanMachine1
@CleanMachine1
Nice!
marchersimon
@marchersimon
Thanks for fixing that @CleanMachine1
Starbeamrainbowlabs
@sbrl
merged
despite the CI failure
CleanMachine1
@CleanMachine1
I didn't do that much lol,
thanks
Perfect, the bot is working again! https://github.com/tldr-pages/tldr/pull/6468#issuecomment-912794926
Starbeamrainbowlabs
@sbrl
:D
pixel aka chrissx
@chrissx:matrix.org
[m]
👏
CleanMachine1
@CleanMachine1
Has someone change the color of the mass changes tag, either I have forgotten or gone colorblind otherwise :smile:
Starbeamrainbowlabs
@sbrl
it's purple I think?
CleanMachine1
@CleanMachine1
Thats what it is, so maybe I just forgot.
Starbeamrainbowlabs
@sbrl
GH's UI has changed a bit recently, making the colours look slightly different
CleanMachine1
@CleanMachine1
Could be, knows really and to be honest who even cares at such a trivial change
More exciting GH news is this https://github.blog/2021-09-01-improving-git-protocol-security-github/
Starbeamrainbowlabs
@sbrl
Oh that's a fascinating insight
CleanMachine1
@CleanMachine1
Why do we have an entire directory for SunOS however other OS's such as BSD-Based don't?
Starbeamrainbowlabs
@sbrl
Historical reasons mostly
But if someone would like to contribute for *bsd, we can always create a new platform
but so far nobody has stepped up
marchersimon
@marchersimon
And another new feature: With --pr you can now view pages from unmerged pull requests directly. If only one page was changed, you can run tldr --pr 1234 or else you get a list of pages to chose from. I hope this will make reviewing pages easier.
And it's easier to spot wrong formatting, because then the page will be messed up :laughing:
2 replies
Starbeamrainbowlabs
@sbrl
ooooh wow
that's an amazing feature
:+1:
marchersimon
@marchersimon
Thanks, if you have any suggestions or ideas just open an issue and I'll take care of it.
Starbeamrainbowlabs
@sbrl
:D
marchersimon
@marchersimon
What do you think about documenting transfer.sh? It's not a command on it's own, but just using curl. But I think it would still be useful.
CleanMachine1
@CleanMachine1
Hey everyone, I am fully back since my ThinkPad is back in working order, feel free to ping for review requests!
marchersimon
@marchersimon
I think we can merge #6383. I already opened an issue to keep track of the missing languages.
1 reply
CleanMachine1
@CleanMachine1

Anyone noticed TLDR is no where near where it was a month or 2 ago?

17 PRs down from what seemed to be always 40+

Should this begin back near hacktoberfest

Starbeamrainbowlabs
@sbrl
Yeah, there's sometimes a lull just before hacktoberfest
marchersimon
@marchersimon
But at least the number of issues went way up :laughing:
Btw when exactly will Hacktoberfest be? I can't find a date online
12 replies
Axel Navarro
@navarroaxel

The git pre-commit hook run scripts/test.sh and now the sh script wants black and flake8 commands in the dev computer. I'm not a python dev and I don't use that commands, I think we should check if black is available before run it. Otherwise we are blocking new contributors to contribute because they need to python stuff.

This was added on September 3rd.

I think the condition should be if $CI==true || <black is available> then <run-black>

Axel Navarro
@navarroaxel
tldr-pages/tldr#6530
Starbeamrainbowlabs
@sbrl
Good thing we moved to GitHub Actions https://arstechnica.com/information-technology/2021/09/travis-ci-flaw-exposed-secrets-for-thousands-of-open-source-projects/
CleanMachine1
@CleanMachine1
Could we get this reviewed or just merged. tldr-pages/tldr#5976
CleanMachine1
@CleanMachine1

Just like to point out in case any issues arise.

I pushed to master, realized my mistake after pushing, rebased and removed the commit with drop

Starbeamrainbowlabs
@sbrl
People may have noticed, but I'm finding the notifications from tldr-pages/tldr impossible to manage. I'd still love to help, but please @mention me for specific requests as to where I'm most helpful, as I'm trailing unwatching the main repo. This means I will receive notifications for the following:
  • Issues/PRs I've already commented on
  • Placed I'm explicitly @mentioned
4 replies
Axel Navarro
@navarroaxel
we should reactivate the TW account to interact in this kind of posts https://twitter.com/nixcraft/status/1439801949545664517
4 replies
marchersimon
@marchersimon
What do you think about asking for the version number of the documented command in the PR template? This could resolve a lot of confusion when different versions of a tool are documented.
Starbeamrainbowlabs
@sbrl
In the PR template, perhaps yeah
In the page itself? I'm not sure that makes sense
Maybe a "version number at the time of writing"
marchersimon
@marchersimon
Yeah, I also wouldn't include it in the page itself. But if we at least would have it in the PR, it would make finding errors easier
Starbeamrainbowlabs
@sbrl
yeah, absolutely
then in a years time or something when we get an issue/pr, we can confirm that the the page is definitely outdated