You use Dependabot to scan dependencies in a GitHub repository. Which two actions will automatically trigger a Dependabot scan? Each correct answer is a complete solution.

Dependabot automatically scans for vulnerabilities and updates dependencies. A scan is triggered when the dependency graph of a repository changes, such as when a new dependency is added or an existing one is updated in a manifest file (e.g., package.json, pom.xml). This ensures that new dependencies are immediately checked. Additionally, Dependabot scans are triggered when a new advisory is published for a dependency already present in the repository. This proactively alerts you to newly discovered vulnerabilities. Creating a pull request or pushing any commit does not automatically trigger a full Dependabot scan for new vulnerabilities, though Dependabot may update its pull requests if a dependency changes. Forking a branch creates a new repository, which would then need Dependabot configured independently.