Search Results for "gss-api"

...Immutable data is unchangeable once created, which makes application development so much simpler. There’s no defensive copying, and you get advanced memoization and change detection techniques with simple logic. Persistent data gives you a mutative API, one that doesn’t update data in-place but always produces new and updated data. The data structures that Immutable.js provides include List, Stack, Map, OrderedMap, Set and more. These structures are highly efficient on modern JavaScript VMs, and minimize the need to cache or copy data.

...Monitor and track PDF file changes, and know when a PDF file has text changes. Know when your favourite product is on sale, or other special deals are announced before anyone else. Detect and monitor changes in JSON API responses.

Watch an object or array for changes. It works recursively, so it will even detect if you modify a deep property.

Changelog CI is a GitHub Action that enables a project to automatically generate changelogs. Changelog CI can be triggered on pull_request, workflow_dispatch, and any other events that can provide the required inputs. Changelog CI uses python and GitHub API to generate a changelog for a repository. First, it tries to get the latest release from the repository (If available). Then, it checks all the pull requests/commits merged after the last release using the GitHub API. After that, it parses the data and generates the changelog. It is able to use Markdown or reStructuredText to generate a Changelog. ...

Github action to retrieve all (added, copied, modified, deleted, renamed, type changed, unmerged, unknown) files and directories. Effortlessly track all changed files and directories relative to a target branch, preceding commit or the last remote commit returning relative paths from the project root using this GitHub action. This action solely identifies files that have undergone changes within the context of events such as pull_request, push, and more. However, it doesn't detect pending...

GitHub Action that enables conditional execution of workflow steps and jobs, based on the files modified by pull request, on a feature branch, or by the recently pushed commits. Run slow tasks like integration tests or deployments only for changed components. It saves time and resources, especially in mono repo setups. GitHub workflow's built-in path filters don't allow this because they don't work on a level of individual jobs or steps.