Texas DPS/DMV Automatic Scheduler

Overview

texas-dps-scheduler

This app will find sameday or nearest 7 day appointments and schedulle it automatically!

Hits DeepScan grade CodeFactor

Top Language Code size License Last commit

image

Why this project exist?

It's so frustrating to get appointments and walk ins so I created this project to gain easier access to DPS and get DL.

Is this illegal?

Honesty, I don't know. Just dont abuse it :)

How to use this project

You can access the wiki here

Comments
  • Doesn't keep checking for locations if none is found

    Doesn't keep checking for locations if none is found

    The requestAvailableLocation function should keep looping if it doesn't find any available locations that match the criteria. My nearest locations aren't always available so it ends up checking for dates with no locations.

    image

    Suggested adding a loop like this in the run method:

    while (this.availableLocation == null || this.availableLocation.length == 0) {
        await this.requestAvailableLocation();
    }
    
    opened by wmortume 5
  • Upgrade @eslint/create-config to version 0.4.1

    Upgrade @eslint/create-config to version 0.4.1


    Welcome to Depfu 👋

    This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

    After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

    Let us know if you have any questions. Thanks so much for giving Depfu a try!


    Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

    What changed?

    ✳️ @​eslint/create-config (^0.3.1 → ^0.4.1) · Repo · Changelog

    Release Notes

    0.4.1

    Documentation

    • d42d866 docs: update --config usage for npm v7+ (#42) (唯然)

    Does any of this look wrong? Please let us know.

    Commits

    See the full diff on Github. The new version differs by 3 commits:


    Depfu Status

    Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

    All Depfu comment commands
    @​depfu rebase
    Rebases against your default branch and redoes this update
    @​depfu recreate
    Recreates this PR, overwriting any edits that you've made to it
    @​depfu merge
    Merges this PR once your tests are passing and conflicts are resolved
    @​depfu close
    Closes this PR and deletes the branch
    @​depfu reopen
    Restores the branch and reopens this PR (if it's closed)
    @​depfu pause
    Ignores all future updates for this dependency and closes this PR
    @​depfu pause [minor|major]
    Ignores all future minor/major updates for this dependency and closes this PR
    @​depfu resume
    Future versions of this dependency will create PRs again (leaves this PR as is)
    depfu 
    opened by depfu[bot] 3
  • Upgrade p-queue to version 7.3.0

    Upgrade p-queue to version 7.3.0


    Welcome to Depfu 👋

    This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

    After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

    Let us know if you have any questions. Thanks so much for giving Depfu a try!


    Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

    What changed?

    ✳️ p-queue (6.6.2 → 7.3.0) · Repo

    Release Notes

    7.3.0

    v7.2.0...v7.3.0

    7.2.0

    v7.1.0...v7.2.0

    7.1.0

    v7.0.0...v7.1.0

    7.0.0

    Breaking

    Improvements

    v6.6.2...v7.0.0

    Does any of this look wrong? Please let us know.

    Commits

    See the full diff on Github. The new version differs by 19 commits:


    Depfu Status

    Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

    All Depfu comment commands
    @​depfu rebase
    Rebases against your default branch and redoes this update
    @​depfu recreate
    Recreates this PR, overwriting any edits that you've made to it
    @​depfu merge
    Merges this PR once your tests are passing and conflicts are resolved
    @​depfu close
    Closes this PR and deletes the branch
    @​depfu reopen
    Restores the branch and reopens this PR (if it's closed)
    @​depfu pause
    Ignores all future updates for this dependency and closes this PR
    @​depfu pause [minor|major]
    Ignores all future minor/major updates for this dependency and closes this PR
    @​depfu resume
    Future versions of this dependency will create PRs again (leaves this PR as is)
    depfu 
    opened by depfu[bot] 2
  • Upgrade chalk to version 5.0.1

    Upgrade chalk to version 5.0.1


    Welcome to Depfu 👋

    This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

    After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

    Let us know if you have any questions. Thanks so much for giving Depfu a try!


    Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

    What changed?

    ✳️ chalk (4.1.2 → 5.0.1) · Repo

    Release Notes

    5.0.1

    • Add main field to package.json for backwards compatibility with some developer tools 85f7e96

    v5.0.0...v5.0.1

    5.0.0

    Breaking

    • This package is now pure ESM. Please read this.
      • If you use TypeScript, you will want to stay on Chalk 4 until TypeScript 4.6 is out. Why.
      • If you use a bundler, make sure it supports ESM and that you have correctly configured it for ESM.
      • The Chalk issue tracker is not a support channel for your favorite build/bundler tool.
    • Require Node.js 12.20 fa16f4e
    • Move some properties off the default export to individual named exports:
      • chalk.InstanceChalk
      • chalk.supportsColorsupportsColor
      • chalk.stderrchalkStderr
      • chalk.stderr.supportsColorsupportsColorStderr
    • Remove .keyword(), .hsl(), .hsv(), .hwb(), and .ansi() coloring methods (#433) 4cf2e40
      • These were not commonly used and added a lot of bloat to Chalk. You can achieve the same by using the color-convert package.
    • The tagged template literal support moved into a separate package: chalk-template (#524) c987c61
    -import chalk from 'chalk';
    +import chalkTemplate from 'chalk-template';
    

    -chalk2 + 3 = {bold ${2 + 3}}; +chalkTemplate2 + 3 = {bold ${2 + 3}};

    Improvements

    v4.1.0...v5.0.0

    Does any of this look wrong? Please let us know.

    Commits

    See the full diff on Github. The new version differs by more commits than we can show here.


    Depfu Status

    Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

    All Depfu comment commands
    @​depfu rebase
    Rebases against your default branch and redoes this update
    @​depfu recreate
    Recreates this PR, overwriting any edits that you've made to it
    @​depfu merge
    Merges this PR once your tests are passing and conflicts are resolved
    @​depfu close
    Closes this PR and deletes the branch
    @​depfu reopen
    Restores the branch and reopens this PR (if it's closed)
    @​depfu pause
    Ignores all future updates for this dependency and closes this PR
    @​depfu pause [minor|major]
    Ignores all future minor/major updates for this dependency and closes this PR
    @​depfu resume
    Future versions of this dependency will create PRs again (leaves this PR as is)
    depfu 
    opened by depfu[bot] 2
  • Upgrade @eslint/create-config to version 0.4.0

    Upgrade @eslint/create-config to version 0.4.0


    Welcome to Depfu 👋

    This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

    After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

    Let us know if you have any questions. Thanks so much for giving Depfu a try!


    Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

    What changed?

    ✳️ @​eslint/create-config (^0.3.1 → ^0.4.0) · Repo · Changelog

    Release Notes

    0.4.0

    Features

    Chores

    • 368a1a3 chore: Remove unused code (#36) (Brandon Mills)

    Does any of this look wrong? Please let us know.

    Commits

    See the full diff on Github. The new version differs by 4 commits:


    Depfu Status

    Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

    All Depfu comment commands
    @​depfu rebase
    Rebases against your default branch and redoes this update
    @​depfu recreate
    Recreates this PR, overwriting any edits that you've made to it
    @​depfu merge
    Merges this PR once your tests are passing and conflicts are resolved
    @​depfu close
    Closes this PR and deletes the branch
    @​depfu reopen
    Restores the branch and reopens this PR (if it's closed)
    @​depfu pause
    Ignores all future updates for this dependency and closes this PR
    @​depfu pause [minor|major]
    Ignores all future minor/major updates for this dependency and closes this PR
    @​depfu resume
    Future versions of this dependency will create PRs again (leaves this PR as is)
    depfu 
    opened by depfu[bot] 1
  • Bookings should be cancelled after a new slot is found

    Bookings should be cancelled after a new slot is found

    Thanks for sharing the project!

    The current behavior of canceling before doing anything is almost never useful: users can cancel the booking themselves before running the program. I imagine the desired behavior is to keep the booking and cancel only when a qualified spot is found.

    opened by eternal-flame-AD 1
  • undici-5.7.0.tgz: 4 vulnerabilities (highest severity is: 9.8) - autoclosed

    undici-5.7.0.tgz: 4 vulnerabilities (highest severity is: 9.8) - autoclosed

    Vulnerable Library - undici-5.7.0.tgz

    An HTTP/1.1 client, written from scratch for Node.js

    Library home page: https://registry.npmjs.org/undici/-/undici-5.7.0.tgz

    Path to dependency file: /package.json

    Path to vulnerable library: /node_modules/undici/package.json

    Vulnerabilities

    | CVE | Severity | CVSS | Dependency | Type | Fixed in | Remediation Available | | ------------- | ------------- | ----- | ----- | ----- | --- | --- | | CVE-2022-35948 | High | 9.8 | undici-5.7.0.tgz | Direct | 5.8.2 | ❌ | | CVE-2022-35949 | High | 9.8 | undici-5.7.0.tgz | Direct | undici - 5.8.2 | ❌ | | CVE-2022-31151 | Medium | 6.5 | undici-5.7.0.tgz | Direct | 5.8.0 | ❌ | | CVE-2022-31150 | Medium | 6.5 | undici-5.7.0.tgz | Direct | 5.8.0 | ❌ |

    Details

    CVE-2022-35948

    Vulnerable Library - undici-5.7.0.tgz

    An HTTP/1.1 client, written from scratch for Node.js

    Library home page: https://registry.npmjs.org/undici/-/undici-5.7.0.tgz

    Path to dependency file: /package.json

    Path to vulnerable library: /node_modules/undici/package.json

    Dependency Hierarchy:

    • :x: undici-5.7.0.tgz (Vulnerable Library)

    Found in base branch: main

    Vulnerability Details

    undici is an HTTP/1.1 client, written from scratch for Node.js.=< [email protected] users are vulnerable to CRLF Injection on headers when using unsanitized input as request headers, more specifically, inside the content-type header. Example: import { request } from 'undici' const unsanitizedContentTypeInput = 'application/json\r\n\r\nGET /foo2 HTTP/1.1' await request('http://localhost:3000, { method: 'GET', headers: { 'content-type': unsanitizedContentTypeInput }, }) The above snippet will perform two requests in a single request API call: 1) http://localhost:3000/ 2) http://localhost:3000/foo2 This issue was patched in Undici v5.8.1. Sanitize input when sending content-type headers using user input as a workaround.

    Publish Date: 2022-08-15

    URL: CVE-2022-35948

    CVSS 3 Score Details (9.8)

    Base Score Metrics:

    • Exploitability Metrics:
      • Attack Vector: Network
      • Attack Complexity: Low
      • Privileges Required: None
      • User Interaction: None
      • Scope: Unchanged
    • Impact Metrics:
      • Confidentiality Impact: High
      • Integrity Impact: High
      • Availability Impact: High

    For more information on CVSS3 Scores, click here.

    Suggested Fix

    Type: Upgrade version

    Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35948

    Release Date: 2022-08-15

    Fix Resolution: 5.8.2

    Step up your Open Source Security Game with Mend here

    CVE-2022-35949

    Vulnerable Library - undici-5.7.0.tgz

    An HTTP/1.1 client, written from scratch for Node.js

    Library home page: https://registry.npmjs.org/undici/-/undici-5.7.0.tgz

    Path to dependency file: /package.json

    Path to vulnerable library: /node_modules/undici/package.json

    Dependency Hierarchy:

    • :x: undici-5.7.0.tgz (Vulnerable Library)

    Found in base branch: main

    Vulnerability Details

    undici is an HTTP/1.1 client, written from scratch for Node.js.undici is vulnerable to SSRF (Server-side Request Forgery) when an application takes in user input into the path/pathname option of undici.request. If a user specifies a URL such as http://127.0.0.1 or //127.0.0.1 js const undici = require("undici") undici.request({origin: "http://example.com", pathname: "//127.0.0.1"}) Instead of processing the request as http://example.org//127.0.0.1 (or http://example.org/http://127.0.0.1 when http://127.0.0.1 is used), it actually processes the request as http://127.0.0.1/ and sends it to http://127.0.0.1. If a developer passes in user input into path parameter of undici.request, it can result in an SSRF as they will assume that the hostname cannot change, when in actual fact it can change because the specified path parameter is combined with the base URL. This issue was fixed in [email protected]. The best workaround is to validate user input before passing it to the undici.request call.

    Publish Date: 2022-08-12

    URL: CVE-2022-35949

    CVSS 3 Score Details (9.8)

    Base Score Metrics:

    • Exploitability Metrics:
      • Attack Vector: Network
      • Attack Complexity: Low
      • Privileges Required: None
      • User Interaction: None
      • Scope: Unchanged
    • Impact Metrics:
      • Confidentiality Impact: High
      • Integrity Impact: High
      • Availability Impact: High

    For more information on CVSS3 Scores, click here.

    Suggested Fix

    Type: Upgrade version

    Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35949

    Release Date: 2022-08-12

    Fix Resolution: undici - 5.8.2

    Step up your Open Source Security Game with Mend here

    CVE-2022-31151

    Vulnerable Library - undici-5.7.0.tgz

    An HTTP/1.1 client, written from scratch for Node.js

    Library home page: https://registry.npmjs.org/undici/-/undici-5.7.0.tgz

    Path to dependency file: /package.json

    Path to vulnerable library: /node_modules/undici/package.json

    Dependency Hierarchy:

    • :x: undici-5.7.0.tgz (Vulnerable Library)

    Found in base branch: main

    Vulnerability Details

    Authorization headers are cleared on cross-origin redirect. However, cookie headers which are sensitive headers and are official headers found in the spec, remain uncleared. There are active users using cookie headers in undici. This may lead to accidental leakage of cookie to a 3rd-party site or a malicious attacker who can control the redirection target (ie. an open redirector) to leak the cookie to the 3rd party site. This was patched in v5.7.1. By default, this vulnerability is not exploitable. Do not enable redirections, i.e. maxRedirections: 0 (the default).

    Publish Date: 2022-07-21

    URL: CVE-2022-31151

    CVSS 3 Score Details (6.5)

    Base Score Metrics:

    • Exploitability Metrics:
      • Attack Vector: Network
      • Attack Complexity: Low
      • Privileges Required: None
      • User Interaction: None
      • Scope: Unchanged
    • Impact Metrics:
      • Confidentiality Impact: Low
      • Integrity Impact: Low
      • Availability Impact: None

    For more information on CVSS3 Scores, click here.

    Suggested Fix

    Type: Upgrade version

    Origin: https://github.com/nodejs/undici/security/advisories/GHSA-q768-x9m6-m9qp

    Release Date: 2022-07-21

    Fix Resolution: 5.8.0

    Step up your Open Source Security Game with Mend here

    CVE-2022-31150

    Vulnerable Library - undici-5.7.0.tgz

    An HTTP/1.1 client, written from scratch for Node.js

    Library home page: https://registry.npmjs.org/undici/-/undici-5.7.0.tgz

    Path to dependency file: /package.json

    Path to vulnerable library: /node_modules/undici/package.json

    Dependency Hierarchy:

    • :x: undici-5.7.0.tgz (Vulnerable Library)

    Found in base branch: main

    Vulnerability Details

    undici is an HTTP/1.1 client, written from scratch for Node.js. It is possible to inject CRLF sequences into request headers in undici in versions less than 5.7.1. A fix was released in version 5.8.0. Sanitizing all HTTP headers from untrusted sources to eliminate \r\n is a workaround for this issue.

    Publish Date: 2022-07-19

    URL: CVE-2022-31150

    CVSS 3 Score Details (6.5)

    Base Score Metrics:

    • Exploitability Metrics:
      • Attack Vector: Network
      • Attack Complexity: Low
      • Privileges Required: None
      • User Interaction: None
      • Scope: Unchanged
    • Impact Metrics:
      • Confidentiality Impact: Low
      • Integrity Impact: Low
      • Availability Impact: None

    For more information on CVSS3 Scores, click here.

    Suggested Fix

    Type: Upgrade version

    Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31150

    Release Date: 2022-07-19

    Fix Resolution: 5.8.0

    Step up your Open Source Security Game with Mend here

    security vulnerability 
    opened by mend-bolt-for-github[bot] 1
  • Upgrade p-queue to version 7.2.0

    Upgrade p-queue to version 7.2.0

    👉 This PR is queued up to get rebased by Depfu


    Welcome to Depfu 👋

    This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

    After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

    Let us know if you have any questions. Thanks so much for giving Depfu a try!


    Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

    What changed?

    ✳️ p-queue (6.6.2 → 7.2.0) · Repo

    Release Notes

    7.2.0

    v7.1.0...v7.2.0

    7.1.0

    v7.0.0...v7.1.0

    7.0.0

    Breaking

    Improvements

    v6.6.2...v7.0.0

    Does any of this look wrong? Please let us know.

    Commits

    See the full diff on Github. The new version differs by 15 commits:


    Depfu Status

    Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

    All Depfu comment commands
    @​depfu rebase
    Rebases against your default branch and redoes this update
    @​depfu recreate
    Recreates this PR, overwriting any edits that you've made to it
    @​depfu merge
    Merges this PR once your tests are passing and conflicts are resolved
    @​depfu close
    Closes this PR and deletes the branch
    @​depfu reopen
    Restores the branch and reopens this PR (if it's closed)
    @​depfu pause
    Ignores all future updates for this dependency and closes this PR
    @​depfu pause [minor|major]
    Ignores all future minor/major updates for this dependency and closes this PR
    @​depfu resume
    Future versions of this dependency will create PRs again (leaves this PR as is)
    depfu 
    opened by depfu[bot] 1
  • Upgrade @types/node to version 18.0.4

    Upgrade @types/node to version 18.0.4


    Welcome to Depfu 👋

    This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

    After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

    Let us know if you have any questions. Thanks so much for giving Depfu a try!


    Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

    What changed?

    ✳️ @​types/node (^17.0.42 → ^18.0.4) · Repo

    Sorry, we couldn't find anything useful about this release.


    Depfu Status

    Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

    All Depfu comment commands
    @​depfu rebase
    Rebases against your default branch and redoes this update
    @​depfu recreate
    Recreates this PR, overwriting any edits that you've made to it
    @​depfu merge
    Merges this PR once your tests are passing and conflicts are resolved
    @​depfu close
    Closes this PR and deletes the branch
    @​depfu reopen
    Restores the branch and reopens this PR (if it's closed)
    @​depfu pause
    Ignores all future updates for this dependency and closes this PR
    @​depfu pause [minor|major]
    Ignores all future minor/major updates for this dependency and closes this PR
    @​depfu resume
    Future versions of this dependency will create PRs again (leaves this PR as is)
    depfu 
    opened by depfu[bot] 1
  • Upgrade @types/node to version 18.0.3

    Upgrade @types/node to version 18.0.3


    Welcome to Depfu 👋

    This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

    After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

    Let us know if you have any questions. Thanks so much for giving Depfu a try!


    Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

    What changed?

    ✳️ @​types/node (^17.0.42 → ^18.0.3) · Repo

    Sorry, we couldn't find anything useful about this release.


    Depfu Status

    Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

    All Depfu comment commands
    @​depfu rebase
    Rebases against your default branch and redoes this update
    @​depfu recreate
    Recreates this PR, overwriting any edits that you've made to it
    @​depfu merge
    Merges this PR once your tests are passing and conflicts are resolved
    @​depfu close
    Closes this PR and deletes the branch
    @​depfu reopen
    Restores the branch and reopens this PR (if it's closed)
    @​depfu pause
    Ignores all future updates for this dependency and closes this PR
    @​depfu pause [minor|major]
    Ignores all future minor/major updates for this dependency and closes this PR
    @​depfu resume
    Future versions of this dependency will create PRs again (leaves this PR as is)
    depfu 
    opened by depfu[bot] 1
  • Upgrade @eslint/create-config to version 0.3.0

    Upgrade @eslint/create-config to version 0.3.0

    👉 This PR is queued up to get rebased by Depfu


    Welcome to Depfu 👋

    This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

    After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

    Let us know if you have any questions. Thanks so much for giving Depfu a try!


    Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

    What changed?

    ✳️ @​eslint/create-config (^0.2.0 → ^0.3.0) · Repo · Changelog

    Release Notes

    0.3.0

    Features

    Does any of this look wrong? Please let us know.

    Commits

    See the full diff on Github. The new version differs by 3 commits:


    👉 No CI detected

    You don't seem to have any Continuous Integration service set up!

    Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

    This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

    • Circle CI, Semaphore and Travis-CI are all excellent options.
    • If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
    • If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

    Depfu Status

    Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

    All Depfu comment commands
    @​depfu rebase
    Rebases against your default branch and redoes this update
    @​depfu recreate
    Recreates this PR, overwriting any edits that you've made to it
    @​depfu merge
    Merges this PR once your tests are passing and conflicts are resolved
    @​depfu close
    Closes this PR and deletes the branch
    @​depfu reopen
    Restores the branch and reopens this PR (if it's closed)
    @​depfu pause
    Ignores all future updates for this dependency and closes this PR
    @​depfu pause [minor|major]
    Ignores all future minor/major updates for this dependency and closes this PR
    @​depfu resume
    Future versions of this dependency will create PRs again (leaves this PR as is)
    depfu 
    opened by depfu[bot] 1
  • Upgrade @eslint/create-config to version 0.4.2

    Upgrade @eslint/create-config to version 0.4.2


    Welcome to Depfu 👋

    This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

    After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

    Let us know if you have any questions. Thanks so much for giving Depfu a try!


    Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

    What changed?

    ✳️ @​eslint/create-config (^0.3.1 → ^0.4.2) · Repo · Changelog

    Release Notes

    0.4.2

    Documentation

    • 561970e docs: sync --config instructions in README with eslint Getting Started (#45) (Milos Djermanovic)

    Chores

    • 66cc96c ci: add Node v19 (#44) (Milos Djermanovic)

    Does any of this look wrong? Please let us know.

    Commits

    See the full diff on Github. The new version differs by 4 commits:


    Depfu Status

    Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

    All Depfu comment commands
    @​depfu rebase
    Rebases against your default branch and redoes this update
    @​depfu recreate
    Recreates this PR, overwriting any edits that you've made to it
    @​depfu merge
    Merges this PR once your tests are passing and conflicts are resolved
    @​depfu close
    Closes this PR and deletes the branch
    @​depfu reopen
    Restores the branch and reopens this PR (if it's closed)
    @​depfu pause
    Ignores all future updates for this dependency and closes this PR
    @​depfu pause [minor|major]
    Ignores all future minor/major updates for this dependency and closes this PR
    @​depfu resume
    Future versions of this dependency will create PRs again (leaves this PR as is)
    depfu 
    opened by depfu[bot] 0
  • Request: More advanced

    Request: More advanced "daysAround"

    We are already able to choose how many days we want the appointment within. However, are we able to make more advanced changes do daysAround, for example, saying I want in appointment within 7-14 days from today?

    enhancement 
    opened by yusufqxzi 1
  • Add a Preferred Time slot

    Add a Preferred Time slot

    Like we have the preferred day, can we have a preferred time slot as well? So that the bot looks for a specific time window. e.g. 8am-10am, 10am-12pm, 12pm-2pm, 2pm-4pm, 4pm-6pm

    opened by tapabrata19 2
Owner
Duy Pham Le
Duy Pham Le
Lightweight, Portable, Flexible Distributed/Mobile Deep Learning with Dynamic, Mutation-aware Dataflow Dep Scheduler; for Python, R, Julia, Scala, Go, Javascript and more

Apache MXNet (incubating) for Deep Learning Apache MXNet is a deep learning framework designed for both efficiency and flexibility. It allows you to m

The Apache Software Foundation 20.2k Jan 5, 2023
Event scheduler is a simple app for viewing the events happening around you

Event scheduler is a simple app for viewing the events happening around you. User can also create their event and include a location. Location can also be marked as hidden(strictly by IV). Built with React and Styled Components

Anselem Odimegwu 3 Mar 29, 2022
Chronos is an ML Scheduler Tool, helping students to block and manage time with minimal manual intervention.

Chronos (Currently in progress) Chronos is an ML Scheduler Tool, helping students to block and manage time with minimal manual intervention. It adapts

Shromann Majumder 3 Aug 17, 2022
This is email scheduler made using MERN. This repo contains server code, client repo is linked in readme.

Email Scheduler Client This is an email scheduler server (client in different repository). It is made using node.js/express.js. Overview User can sign

Sai Charan 2 Dec 3, 2022
cis-scheduler-team-26 created by GitHub Classroom

React TypeScript Starter Repo Hello! This repository has been pre-configured with eslint and gh-pages to automatically deploy your app when you push t

UD CISC275 Spring 2022 1 Sep 4, 2022
This is an email scheduler made using MERN stack. This repo contains client, server side is linked in readme

Email Scheduler Client This is an email scheduler client (server in different repository). It is made using react. Overview User can sign-up/sign-in,

Sai Charan 3 Dec 3, 2022
A free and open-source Automatic Account Creator (AAC) written in Javascript Stack;

A free and open-source Automatic Account Creator (AAC) written in Javascript Stack. ????‍?? Techs Front-end Vue.js Vuex-module-decorators Vuetify.js N

null 24 Dec 17, 2022
Automatic arxiv->ar5iv link replacement in Chrome.

Automatic arxiv->ar5iv link replacement in Chrome. This chrome extension will automatically replace arxiv.org/pdf/* links with ar5iv links for more we

yobi byte 44 Oct 29, 2022
An interface for an Automatic Ticket Vending Machine

ATVM-INTERFACE It is an interface for an Automatic Ticket Vending Machine. Try The Web Application! - Book your Ticket At Railway Stations, ATVMs (Aut

AMEY THAKUR 7 Apr 28, 2022
Waypoint - Automatic Table of Contents Generator for Obsidian.md

Waypoint - Automatic Table of Contents Generator for Obsidian.md Do you use folders to categorize your notes and wish that Obsidian would show certain

Idrees 153 Jan 2, 2023
🚀 Create dynamic and automatic changelogs for your project!

Versionator-js Create dynamic and automatic changelogs for your project!. Installation Use the package manager npm to install versionator-js. npm inst

Diego Sousa 6 Jan 6, 2023
Automatic Role Adder Is Usually Used In Coding Servers Which Give Access To Codes By Subbing To Their Channel So This Helps Them To Auto Role People :)

Automatic Role Adder Setup Guide Automatic Role Adder Is Usually Used In Coding Servers Which Give Access To Codes By Subbing To Their Channel So This

NotJust 25 Dec 23, 2022
🪄 Automatic backups for your Notion workspaces.

Notion Backups Set up automated backups for your Notion workspaces that run on a time-basis and notify you by Slack, Discord, or email, so you never w

NotionStuff 26 Aug 7, 2022
It is automatic mongodb data backup with cronjob.

Do you need my help? Visit our Discord server. Installation npm i mongoose-backup --save yarn add mongoose-backup Guide const MongoBackuper = require(

Void Development 3 Aug 8, 2022
chakra-radix-colors provides radix-ui color palettes, automatic dark mode, and acessible colors to chakra-ui applications

chakra-radix-colors chakra-radix-colors provides radix-ui color palettes, automatic dark mode, and acessible colors to chakra-ui applications. About C

null 11 Dec 30, 2022
automatic poits grabber for twitch, works with all supported langauges on twitch

Twitch Points Grabber It’s an extension for edge, is aviable in the microsoft Edge Add-ons. This extension will collect any channel points. Settings I

Claudio Menegotto 3 Nov 28, 2022
🍺 Integrates Laravel Pint into your VSCode projects for automatic code formatting

Laravel Pint for VS Code This extension is NOT official from the Laravel team. Take a look into the official project. Integrates Laravel Pint into you

Open Southeners 34 Dec 8, 2022
Automatic Daily Login Rewards (Multiple Accounts); Export wish history

Genshin Automation This tool will automatically collect Hoyolab daily login rewards. Using this tool you can: Automate your rewards on the Hoyolab web

salem 27 Dec 21, 2022
A base project for Express with Typescript to create an API. Includes automatic input validation and Swagger UI generation.

(Typescript) Express API with input Validation and Swagger UI Thats a mouthful isn't it. Typescript: The language used, a superset of Javascript with

Tjeerd Bakker 6 Oct 26, 2022