profile
viewpoint

lo1tuma/eslint-plugin-mocha 245

ESLint rules for mocha

0xPIT/cubemeter 12

CubeMeter, a node.js smart meter platform

lo1tuma/eslint-plugin-ramda 10

Moved to https://github.com/ramda/eslint-plugin-ramda

joyn/eslint-config 2

Shareable ESLint config presets for Joyn.

koelly/Mensa 1

Android App die den Speiseplan der Mensen in Niederbayern/Oberpfalz anzeigt

lo1tuma/ava 0

🚀 Futuristic JavaScript test runner

lo1tuma/bluebird 0

Bluebird is a full featured promise library with unmatched performance.

lo1tuma/chai 0

BDD / TDD assertion framework for node.js and the browser that can be paired with any testing framework.

lo1tuma/connect 0

Connect is a middleware layer for Node.js

pull request commenteslint/eslint-release

Update: group commits by types in release log (fixes #46)

Thanks for doing this! We need the team’s input before merging but I’m in favor. 👍

sapphi-red

comment created time in 2 days

startedlo1tuma/eslint-plugin-mocha

started time in 3 days

PR opened eslint/eslint-release

Fix: env var names are case-insensitive in windows

Tests were not passing in my environment while implementing #47. I am using windows and my path env name was Path (not PATH). This caused env.PATH to be undefined. Accessing process.env.PATH returns the correct value. This PR fixes this by handling all env names as uppercased names in windows.

+7 -2

0 comment

1 changed file

pr created time in 3 days

pull request commenteslint/eslint-release

Update: group commits by types in release log (closes #46)

Hi @sapphi-red!, thanks for the Pull Request

The first commit message isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.

  • The issue reference must be formatted as follows:

    If the pull request addresses an issue, then the issue number should be mentioned at the end. If the commit doesn't completely fix the issue, then use (refs #1234) instead of (fixes #1234).

    Here are some good commit message summary examples:

    Build: Update Travis to only test Node 0.10 (refs #734)
    Fix: Semi rule incorrectly flagging extra semicolon (fixes #840)
    Upgrade: Esprima to 1.2, switch to using comment attachment (fixes #730)
    

Read more about contributing to ESLint here

sapphi-red

comment created time in 3 days

delete branch screendriver/gitlab-pipeline-deleter

delete branch : renovate/sinon-9.x

delete time in 3 days

push eventscreendriver/gitlab-pipeline-deleter

Renovate Bot

commit sha f1bdac76d6c4f3b0577fe1a98fd6c125c1017a5d

chore(deps): update dependency @types/sinon to v9.0.9

view details

push time in 3 days

issue commenteslint/eslint-release

In release log, group commits by types like blog post

I will submit a PR!

sapphi-red

comment created time in 3 days

push eventlo1tuma/pr-log

Renovate Bot

commit sha 8cdb54836a3fd4c56785b0dbf8c11531fcb8b260

⬆️ Update dependency eslint-config-joyn to v0.13.0

view details

push time in 3 days

create barnchscreendriver/gitlab-pipeline-deleter

branch : renovate/sinon-9.x

created branch time in 3 days

PR opened joyn/eslint-config

Reviewers
Set @typescript-eslint/array-type to "array"
+1 -1

0 comment

1 changed file

pr created time in 3 days

create barnchjoyn/eslint-config

branch : typescript-array-type

created branch time in 3 days

issue commenteslint/eslint-release

In release log, group commits by types like blog post

I was actually thinking about this, too, so I’m 👍

@sapphi-red would you be open to submitting a PR for this?

sapphi-red

comment created time in 4 days

push eventlo1tuma/pr-log

Renovate Bot

commit sha 6803f18c16a1203ae3103a744a9889d760d82cb9

⬆️ Update babel monorepo

view details

push time in 4 days

delete branch screendriver/gitlab-pipeline-deleter

delete branch : renovate/eslint-packages

delete time in 4 days

push eventscreendriver/gitlab-pipeline-deleter

Renovate Bot

commit sha de648519d3f1011325ca0581252a18522aea9c64

chore(deps): update eslint packages to v4.8.2

view details

push time in 4 days

create barnchscreendriver/gitlab-pipeline-deleter

branch : renovate/eslint-packages

created branch time in 4 days

delete branch screendriver/gitlab-pipeline-deleter

delete branch : jsx-transform

delete time in 4 days

push eventscreendriver/gitlab-pipeline-deleter

Christian Rackerseder

commit sha b0cc966f9b992025ea88f04db4643444384eea7a

refactor: use React 17 new JSX transform

view details

Christian Rackerseder

commit sha 580cec142e3678e4fdd026196281e2ade6d948a4

Merge pull request #29 from screendriver/jsx-transform

view details

push time in 4 days

delete branch screendriver/gitlab-pipeline-deleter

delete branch : checked-indexed-accesses

delete time in 4 days

push eventscreendriver/gitlab-pipeline-deleter

Christian Rackerseder

commit sha 3085670f4c1983be43ba9865647dba2808b86f9d

build: enable checked indexed accesses

view details

Christian Rackerseder

commit sha 35c414bdec56975562910a3f2bd4873601b0d5b7

Merge pull request #30 from screendriver/checked-indexed-accesses

view details

push time in 4 days

push eventscreendriver/gitlab-pipeline-deleter

Christian Rackerseder

commit sha b0cc966f9b992025ea88f04db4643444384eea7a

refactor: use React 17 new JSX transform

view details

push time in 4 days

issue openedeslint/eslint-release

In release log, group commits by types like blog post

Hello, thanks for developing eslint!

Currently both of the changelog and the release log just lists the commits straight through. I am using dependabot to maintain my repository dependencies and it shows the changelog and the release log in PRs like this (https://github.com/traPtitech/traQ_S-UI/pull/1614). I wonder if the release log becomes the format of blog posts: commits grouped by change types. This will make it easy to check whether the version bump will affect my code. Not everyone uses dependabot, but could you consider it?

created time in 4 days

pull request commentscreendriver/gitlab-pipeline-deleter

Enable checked indexed accesses

Codecov Report

Merging #30 (3085670) into main (fee0a69) will not change coverage. The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##              main       #30   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            4         4           
  Lines          219       219           
  Branches        43        43           
=========================================
  Hits           219       219           

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update fee0a69...3085670. Read the comment docs.

screendriver

comment created time in 4 days

create barnchscreendriver/gitlab-pipeline-deleter

branch : checked-indexed-accesses

created branch time in 4 days

pull request commentscreendriver/gitlab-pipeline-deleter

Use React 17 new JSX transform

Codecov Report

Merging #29 (5cfe925) into main (fee0a69) will not change coverage. The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff            @@
##              main       #29   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            4         4           
  Lines          219       219           
  Branches        43        43           
=========================================
  Hits           219       219           
Impacted Files Coverage Δ
src/App.tsx 100.00% <100.00%> (ø)
src/Error.tsx 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update fee0a69...5cfe925. Read the comment docs.

screendriver

comment created time in 4 days

more