Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jun 21 13:06
    captn3m0 synchronize #1339
  • Jun 21 13:06

    captn3m0 on mssqlserver-labelling

    (compare)

  • Jun 21 13:06

    captn3m0 on mssqlserver

    [mssql] Improve Labels Uses re… (compare)

  • Jun 21 13:06
    captn3m0 closed #1340
  • Jun 21 12:44

    github-actions[bot] on submodules

    (compare)

  • Jun 21 12:44

    github-actions[bot] on master

    Bump _data/release-data from `2… 🤖: Update latest release data (compare)

  • Jun 21 12:44
    github-actions[bot] closed #1342
  • Jun 21 12:39
    github-actions[bot] auto_merge_enabled #1342
  • Jun 21 12:39
    github-actions[bot] synchronize #1342
  • Jun 21 12:39

    github-actions[bot] on submodules

    🤖: Update latest release data (compare)

  • Jun 21 12:38
    dependabot[bot] labeled #1342
  • Jun 21 12:38
    dependabot[bot] labeled #1342
  • Jun 21 12:38
    dependabot[bot] opened #1342
  • Jun 21 12:38

    dependabot[bot] on submodules

    Bump _data/release-data from `2… (compare)

  • Jun 21 12:19
    BiNZGi closed #1341
  • Jun 21 12:19
    BiNZGi commented #1341
  • Jun 21 12:02
    turbolego labeled #1341
  • Jun 21 12:02
    welcome[bot] commented #1341
  • Jun 21 12:02
    turbolego opened #1341
  • Jun 21 11:34
    captn3m0 commented #1339
HanzoAndTheDark
@HanzoAndTheDark
Oieeh...
Alguém ai ?
To pensando em criar uma ferramenta alguém ai se interessa ?
Evernow
@danielsuarez369:matrix.org
[m]

Hi.

For the automatic update github actions setup, does all the Ruby scripts do is update the appropriate json files, and then committed? I ask as I am not familiar with Ruby, but I can automate a few releases using Python.

Wondering if it's appropriate for a Python script to be run in the "Update Release data" action after Ruby, which simply updates the json it wants to, and then the rest of the action can do the work of updating the website.

mcandre
@mcandre
hi, i'm prototyping a command line tool to apply the endoflife database as a linter: https://github.com/mcandre/cicada
mcandre
@mcandre
i think the exit status behavior is suitable for an enterprisey CI/CD setup. however, for local development expect to see warnings for the quite old editions of ruby, python, and friends that major operating systems continue to install by default at system level (!)

i have tried my best to populate CLI queries for the most common operating systems and applications, so that the linter can fetch the live version numbers for comparison with the end of life database. maybe 20% complete there.

would love to see the database grow to include standard, portable commands for obtaining the live version info. i believe the db would see more testing, and attention to detail than the downstream linter config.

mcandre
@mcandre
the API is a lil wonky to consume in strongly typed languages. would like to see single-typed editions of the common fields, for easier JSON -> in-memory non-JavaScript programming language object. like, go ahead and format all versions as strings, for example, instead of a mixture of numbers and strings
BiNZGi
@BiNZGi
Thanks @mcandre for your messages and contratulations on starting your new project.
To get more attention for your mentioned points I propose to open a new github issue.