libphonenumber

432 MiB

Tree: 4693d8550d

Author	SHA1	Message	Date
dependabot[bot]	4693d8550d	Bump github/codeql-action from 2.2.9 to 2.21.1 (#3136 ) Bumps [github/codeql-action](https://github.com/github/codeql-action) from 2.2.9 to 2.21.1. - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](`04df1262e6`...6ca1aa8c195c3ca3e77c174fe0356db1bce3b319) --- updated-dependencies: - dependency-name: github/codeql-action dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2 years ago
penmetsaa	7118649940	Adding Code Owners So the approvers were organized (#2995 )	3 years ago
StepSecurity Bot	02559a8541	[StepSecurity] Apply security best practices (#2913 ) * [StepSecurity] Apply security best practices Signed-off-by: StepSecurity Bot <bot@stepsecurity.io> * Update codeql.yml * Update codeql.yml --------- Signed-off-by: StepSecurity Bot <bot@stepsecurity.io> Co-authored-by: penmetsaa <penmetsaa@google.com>	3 years ago
penmetsaa	83045b03bf	Remove old ci/cd configs (#2691 )	4 years ago
penmetsaa	55fa7ba823	Update event list for workflow triggering. (#2665 ) - When configured "pull_request[type: opened] + push", workflow not getting triggered when there is a change in PR code/commits when the branch is from the parent's forked repo. - Configured only pull_request event as any change can only go through PR. - pull_request event by default happens when opened, synchronize (means whenever there is change/commit, sync happens), and reopened. So this should be good enough for our use cases. More details in [approach doc](https://docs.google.com/document/d/1YNYUAlEUXTi4UZG5gEFZGQ7oe7LxNKh7FYSg2qtIUvI/edit#heading=h.1c7qt5y1jb9)	4 years ago
penmetsaa	c930db20e1	Configure CI flow in Github Actions (#2664 ) Our objective is to (replicating the previous setup): - Do Maven test of LPN tool modules common, data and java-build through a Maven profile. - Also build and test run ant target “junit” that unit tests the java LPN api jar after being built. - Check whether LPN’s JS API/files are in ascii format/not. - More details are mentioned in [approach doc](https://docs.google.com/document/d/1YNYUAlEUXTi4UZG5gEFZGQ7oe7LxNKh7FYSg2qtIUvI/edit)	4 years ago

6 Commits (4693d8550d3f198ceda14f9e88fe030e792c418a)