-
-
Notifications
You must be signed in to change notification settings - Fork 0
8 inconsistent lead generation from seed urls and user agents #17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8 inconsistent lead generation from seed urls and user agents #17
Conversation
- Deleted test_calllist_output.sh: Integration test for calllist CSV generation. - Deleted test_config_defaults.sh: Verification of default configuration values. - Deleted test_end_sequence_dry_run.sh: Smoke test for end_sequence.sh dry-run functionality. - Deleted test_fetch_behaviour.sh: Tests for fetch.sh behaviors including robots.txt and CAPTCHA detection. - Deleted test_geography_seed_check.sh: Validation of .com.au domains in seeds.csv. - Deleted test_load_fetch_config.sh: Verification of fetch configuration loading from INI files. - Deleted test_log_rotate.sh: Smoke test for log_rotate.sh dry-run. - Deleted test_on_err_writes_status.sh: Verification of error handling in scripts. - Deleted test_prereqs.sh: Check for essential tools availability. - Deleted test_update_readme.sh: Smoke test for README update script. - Deleted unit_archive_cleanup_summarise.sh: Tests for archiving and cleanup scripts. - Deleted unit_fetch_ua_403.sh: Tests for User-Agent rotation and 403 retry behavior. - Deleted unit_load_config.sh: Tests for loading environment and configuration. - Deleted unit_normalize_split_extract.sh: Tests for normalization and extraction scripts. - Deleted unit_paginate_sleep_marker.sh: Tests for pagination with sleep commands. - Deleted unit_parse_html_json.sh: Tests for parsing HTML and embedded JSON. - Deleted unit_pick_pagination_extract.sh: Tests for pagination and seed extraction. - Deleted unit_prepare_log.sh: Tests for log preparation script. - Deleted unit_retry_heal.sh: Tests for retry and healing mechanisms. - Deleted unit_validate_env.sh: Tests for environment variable validation.
…ndling; update usage documentation and seed data
…nd comprehensive test suite; update user agent and seed URL files
…ization, logging, and error handling; update user agent and seed URLs for improved consistency
- Clarified history handling and added configuration notes in README and CHANGELOG. - Updated usage instructions for appending history and error handling. - Improved test scripts to utilize fixture files for user agents, ensuring isolation and consistency. - Added new test for ensuring user agent file immutability during operations.
…istory, enhance documentation, and add tests for default configurations
…h temporary files, update documentation, and improve test fixtures for better isolation
…onboarding, code review, and wiki generation; improve POSIX portability in scripts and documentation
…craper - Introduced Acknowledgments, Changelog, and Citation files. - Added CODEOWNERS, Code of Conduct, and Contribution guidelines. - Created SECURITY and SUPPORT documents for user assistance. - Implemented UPGRADING and USAGE documentation for version management and usage instructions. - Established a structured documentation framework with tutorials, how-to guides, and reference materials. - Updated README with improved project overview and features. - Enhanced portability documentation and clarified configuration options. - Added new test fixtures and updated existing ones for better coverage. - Updated company history and user agent files for testing.
…rements for non-technical users
…hange script permissions
…ement CRLF detection script
… VSCode extensions
…entation Standards across docs and wiki
…documentation standards - Introduced a new agent: Ultimate Transparent Thinking Beast Mode with comprehensive operational directives for maximum creativity and transparency. - Updated documentation standards across multiple files to improve clarity and accessibility, ensuring inclusion of PDL pseudocode and diagrams (PlantUML/Mermaid) for better understanding. - Enhanced formatting for readability in various markdown files, including Acknowledgments, Agent, Changelog, Contributing, Contributors, Installation, Portability, README, Security, Support, Upgrading, Usage, and various documentation guides.
…xing, specifications, and coding standards - Create `tldr-prompt.prompt.md` for generating tldr summaries from GitHub Copilot files and documentation. - Add `update-implementation-plan.prompt.md` to facilitate updates to implementation plans based on new requirements. - Introduce `update-markdown-file-index.prompt.md` for updating markdown files with an index of files from specified folders. - Implement `update-specification.prompt.md` for updating existing specification files to align with new requirements. - Develop `write-coding-standards-from-file.prompt.md` to generate coding standards documents based on existing files and styles.
…ve agent guidance and wiki references
…hensive company and URL lists for defence jobs
…tallation, portability, usage, support, upgrading, and coding standards for the Elvis project
…glossary for better user guidance
…ning goals, user personas, and functional requirements
…ty and functionality
…onality - Removed obsolete tools from plan.agent.md and updated tool lists in planner.agent.md, prd.agent.md, principal-software-engineer.agent.md, and specification.agent.md to reflect current usage. - Introduced a new prompt-builder.agent.md for expert prompt engineering and validation. - Deleted task-planner.agent.md and task-researcher.agent.md as part of streamlining agent functionalities. - Updated code-review-generic.instructions.md to exclude the coding-agent from generic instructions. - Corrected localization.instructions.md to link to the correct issue tracker for reporting translation errors.
…ved lead generation
…O list for improved tracking and compliance
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This pull request introduces foundational repository improvements focused on workflow standardization, issue management, code quality enforcement, and agent documentation. The changes establish GitHub repository infrastructure to streamline collaboration, ensure compliance, and enhance the developer experience.
Changes:
- Added standardized pull request and issue templates to guide contributors through submission processes
- Implemented ESLint configuration with security plugins and Prettier integration
- Created funding configuration to enable project sponsorship
- Added detailed agent workflow documentation for automated problem-solving
Reviewed changes
Copilot reviewed 174 out of 266 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
.github/PULL_REQUEST_TEMPLATE.md |
Template to standardize PR summaries, checklists, and issue references |
.github/FUNDING.yml |
Configuration file enabling GitHub Sponsors and other funding platforms |
.github/ISSUE_TEMPLATE/bug_report.md |
Structured bug report template with compliance requirements |
.github/ISSUE_TEMPLATE/feature_request.md |
Markdown-based feature request template |
.github/ISSUE_TEMPLATE/feature_request.yml |
YAML-based feature request template with form fields |
.github/ISSUE_TEMPLATE/config.yml |
Configuration for issue template options and external links |
.eslintrc.json |
ESLint configuration with recommended rules and security plugins |
.github/agents/4.1-Beast.agent.md |
Agent definition and autonomous workflow instructions |
CODEOWNERS |
Code ownership mapping for review automation |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This pull request introduces several foundational improvements to the project's GitHub repository, focusing on workflow standardization, issue and feature request management, code quality enforcement, and agent documentation. These changes help streamline collaboration, ensure compliance, and improve the overall developer experience.
Repository workflow and documentation:
.github/PULL_REQUEST_TEMPLATE.mdto guide contributors on summaries, checklists, and related issues..github/FUNDING.ymlto facilitate project sponsorship.Issue and feature request management:
.github/ISSUE_TEMPLATE/bug_report.md), feature requests (.github/ISSUE_TEMPLATE/feature_request.md,.github/ISSUE_TEMPLATE/feature_request.yml), and a configuration file to manage issue template options (.github/ISSUE_TEMPLATE/config.yml). These templates enforce compliance, security, and contribution guidelines for all submissions. [1] [2] [3] [4]Code quality and linting:
.eslintrc.jsonwith recommended rules, security plugin, and Prettier integration to enforce code style, best practices, and security standards.Agent documentation:
.github/agents/4.1-Beast.agent.md, outlining autonomous problem-solving steps, research requirements, and communication guidelines for coding agents.