Skip to content

Neo4j dev database type needs Neo4j Harness just like how relational dev database types have h2 #1968

Neo4j dev database type needs Neo4j Harness just like how relational dev database types have h2

Neo4j dev database type needs Neo4j Harness just like how relational dev database types have h2 #1968

Workflow file for this run

#
# Copyright the original author or authors from the JHipster project.
#
# This file is part of the JHipster project, see https://www.jhipster.tech/
# for more information.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# https://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
name: Cleanup Labels
on:
issues: { types: [closed] }
jobs:
remove-labels:
runs-on: ubuntu-latest
steps:
- uses: actions/github-script@v7
with:
github-token: ${{secrets.GITHUB_TOKEN}}
script: |
const issue = { owner: context.issue.owner, repo: context.issue.repo, issue_number: context.issue.number }
github.rest.issues.listLabelsOnIssue({...issue}).then(response => {
const labels = response.data
for (const label of labels) {
if (label.name == 'area: needs-reproduction' || label.name == 'area: waiting for information' || label.name.includes('status: ')) {
github.rest.issues.removeLabel({...issue, name: label.name})
}
}
})