Skip to content
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.

Sign up for GitHub

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

Jump to bottom

RHINENG-2610: use latest_repo_change timestamp for repo based re-eval #1334

Merged
merged 1 commit into from
Nov 6, 2023
Merged

RHINENG-2610: use latest_repo_change timestamp for repo based re-eval #1334

merged 1 commit into from
Nov 6, 2023

Conversation

psegedy
Copy link
Member

@psegedy psegedy commented Nov 3, 2023

Secure Coding Practices Checklist GitHub Link

Secure Coding Checklist

  • Input Validation
  • Output Encoding
  • Authentication and Password Management
  • Session Management
  • Access Control
  • Cryptographic Practices
  • Error Handling and Logging
  • Data Protection
  • Communication Security
  • System Configuration
  • Database Security
  • File Management
  • Memory Management
  • General Coding Practices

@jira-linking Jira Linking
Copy link

jira-linking bot commented Nov 3, 2023

Referenced Jiras:
https://issues.redhat.com/browse/RHINENG-2610

@psegedy psegedy requested a review from MichaelMraka November 3, 2023 15:40
@psegedy psegedy force-pushed the repobased branch 2 times, most recently from 3882838 to c60f414 Compare November 6, 2023 10:50
@psegedy psegedy merged commit 9dc4dd3 into RedHatInsights:master Nov 6, 2023
3 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@MichaelMraka MichaelMraka MichaelMraka approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@psegedy @MichaelMraka